|
Vixie Cron "do_command.c" setuid Security Issue
|
|
Secunia Advisory:
|
SA20380
|
|
|
Release Date:
|
2006-06-01
|
|
Popularity:
|
6,777 views
|
|
|
Critical:
|
Less critical
|
|
Impact:
|
Privilege escalation
|
|
Where:
|
Local system
|
|
Solution Status:
|
Unpatched
|
|
| Software: | Vixie Cron 4.x
|
|
|
Subscribe:
|
Instant alerts on relevant vulnerabilities 
|
|
| CVE reference: | CVE-2006-2607
|
|
Description:
Roman Veretelnikov has reported a security issue in Vixie Cron, which potentially can be exploited by malicious, local users to perform certain actions with escalated privileges.
The security issue is caused due to missing checks for whether the "setuid()" call has succeeded before running a job submitted by a user. This may cause the user's job to run with root privileges if the "setuid()" fails due to e.g. PAM failures or resource limits.
The security issue has been reported in version 4.1. Other versions may also be affected.
Solution:
Restrict the use of cron to trusted users only.
Some Linux vendors have issued fixed packages.
Provided and/or discovered by:
Roman Veretelnikov
Original Advisory:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=178431
http://bugs.gentoo.org/show_bug.cgi?id=134194
|
|
|
Track this Secunia Advisory
|
Customers of the Secunia Vulnerability Intelligence solutions will automatically receive updates when new information regarding this advisory is released.
Read more about our Vulnerability Intelligence solutions and what they can do for you and your company.
|
|
|
About this Secunia Advisory
|
Please note: The information that this Secunia Advisory is based on comes from a third party unless stated otherwise.
Secunia collects, validates, and verifies all vulnerability reports issued by security research groups, vendors, and others.
|
