Bug 162022 - CVE-2005-1038 vixie-cron information leak
CVE-2005-1038 vixie-cron information leak
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: vixie-cron (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Jason Vas Dias
Brock Organ
: Security
Depends On:
Blocks: 163888 168424
  Show dependency treegraph
Reported: 2005-06-29 03:32 EDT by Mark J. Cox (Product Security)
Modified: 2007-11-30 17:07 EST (History)
2 users (show)

See Also:
Fixed In Version: RHSA-2006-0117
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-03-15 10:31:08 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Mark J. Cox (Product Security) 2005-06-29 03:32:38 EDT
+++ This bug was initially created as a clone of Bug #154920 +++

crontab in Vixie cron 4.1, when running with the -e option, allows local users
to read the cron files of other users by changing the file being edited to a
symlink.  NOTE: there is insufficient information to know whether this is a
duplicate of CVE-2001-0235.

Comment 2 Josh Bressers 2005-07-08 17:25:15 EDT
Our current fix for this issue is not complete.  A race condition still exists
between the time we lstat the file in question, and when we open the file.
Comment 3 Jason Vas Dias 2005-07-11 19:37:05 EDT
This is now fixed with vixie-cron-4.1-8.EL3, available from:
The race condition has been circumvented: the fopen() is done as
the non-root user, which also fixes the case when the temporary
file is made into a hardlink to a root owned file.
Please try out the new version and let me know of any issues - thanks.

Comment 6 Jason Vas Dias 2005-10-14 11:32:26 EDT
This bug is fixed with vixie-cron-4.1-8_EL3, available from:
and should be considered for inclusion in RHEL-3-U7 .
Comment 13 Red Hat Bugzilla 2006-03-15 10:31:09 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.