[1682] in linux-security and linux-alert archive
[linux-security] The never ending story of buffer overruns in cron(tab)
daemon@ATHENA.MIT.EDU (Jason Haar)
Thu Dec 11 03:08:03 1997
From: Jason Haar <Jason.Haar@trimble.co.nz>
To: linux-security@redhat.com
Cc: ewt@redhat.com, marc@redhat.com
Date: Thu, 11 Dec 1997 11:18:53 +1300
Resent-From: linux-security@redhat.com
Reply-To: linux-security@redhat.com
[Mod: FYI - i have not looked at it yet. I am not going to approve anything
on this topic until someone from redhat comments on it or until someone
really goes though the code -- alex]
[Mod: ewt@redhat.com and marc@redhat.com added to the Cc: list -- alex]
Hi there
I saw there was a new redhat vixie-cron available (vixie-cron-3.0.1-19.src.rpm,
dated Nov 10), and given the number of buffer overruns I've seen this year
in everything, I downloaded it to have a look. It looks very similar to the
one I was running (cron-3.0pl1), so I dug deeper... They both still appear
to use sprintf instead of snprintf's everywhere!
I went back through my old BUGTRAQ/Linux Security mail messages of the
past year, and there were several pointing out sprintf problems in cron
back in Dec last year. Sure enough, none of those had shown up in the
"newer" crons!
I have patched them into my current cron now, but can someone tell me why
is it still like this? Surely all new cron* distributions should have such
holes fixed by now?
Cheers
--
Jason Haar, Unix/Networking Specialist, Trimble Navigation New Zealand
Phone: +64 3 3391377 Fax: +64 3 3391417
--
----------------------------------------------------------------------
Please refer to the information about this list as well as general
information about Linux security at http://www.aoy.com/Linux/Security.
----------------------------------------------------------------------
To unsubscribe: mail -s unsubscribe test-list-request@redhat.com < /dev/null
