CVE-2006-2607 json
do_command.c in Vixie cron (vixie-cron) 4.1 does not check the return code of a setuid call, which might allow local users to gain root pri…
published 2006-05-25 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-2606
- cvss
- 7.2
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 47%
- public exploits
- 0
- none known
Summary
do_command.c in Vixie cron (vixie-cron) 4.1 does not check the return code of a setuid call, which might allow local users to gain root privileges if setuid fails in cases such as PAM failures or resource limits, as originally demonstrated by a program that exceeds the process limits as defined in /etc/security/limits.conf.
Patch / fix
- cron Debian 14, Debian 13, Debian 12 3.0pl1-64
debian advisories DEBIAN-CVE-2006-2607
- vixie-cron RHEL 4 4:4.1-44.EL4
red hat advisories RHSA-2006:0539
- cronie openSUSE Tumbleweed 1.5.0-65.4
opensuse advisories openSUSE-SU-2024:10139-1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2006-2607 updated
Jobs start from root when pam_limits enabled
-
Red Hat Enterprise Linux AS version 4 vixie-cron 4.1-44.EL4 Red Hat Enterprise Linux Desktop version 4 vixie-cron 4.1-44.EL4 Red Hat Enterprise Linux ES version 4 vixie-cron 4.1-44.EL4 Red Hat Enterprise Linux WS version 4 vixie-cron 4.1-44.EL4fixed: vendor fix RHSA-2006:0539
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.56% chance of exploitation in the next 30 days, higher than 47% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- bugzilla.redhat.com https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=178431 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
References
-
bugzilla.redhat.com
/bugzilla/show_bug.cgi?id=178431
exploit, patch
-
usn.ubuntu.com
/778-1/
vendor-advisory
-
novell.com
/linux/security/advisories/2006-05-32.html
vendor-advisory
-
security.gentoo.org
/glsa/glsa-200606-07.xml
vendor-advisory
-
redhat.com
/support/errata/RHSA-2006-0539.html
vendor-advisory
-
secunia.com
/advisories/20380
third-party-advisory, vendor-advisory
-
securityfocus.com
/archive/1/435033/100/0/threaded
mailing-list
-
vupen.com
/english/advisories/2006/2075
vdb-entry
- support.avaya.com /elmodocs2/security/ASA-2006-168.htm
-
securityfocus.com
/bid/18108
vdb-entry
- bugs.gentoo.org /show_bug.cgi?id=134194
-
secunia.com
/advisories/20388
third-party-advisory
-
securitytracker.com
/id?1016480
vdb-entry
-
secunia.com
/advisories/35318
third-party-advisory
-
secunia.com
/advisories/21032
third-party-advisory
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A10213
vdb-entry, signature
-
exchange.xforce.ibmcloud.com
/vulnerabilities/26691
vdb-entry
-
secunia.com
/advisories/20616
third-party-advisory
-
secunia.com
/advisories/21702
third-party-advisory
Sources
- CVE List CVE-2006-2607
- NVD CVE-2006-2607
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.