CVE-1999-0872: Buffer Overflow
Buffer overflow in Vixie cron allows local users to gain root access via a long MAILTO environment variable in a crontab file.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
Configure cron to ignore MAILTO environment variables in crontab files or enforce a maximum allowable length for MAILTO entries so that excessively long values cannot trigger a buffer overflow.
Vixie cron MAILTO environment handling = disable or limit MAILTO length - Compensating control
Restrict which local users can create or edit crontab files: tighten filesystem permissions/ACLs on per-user crontab locations (for example /var/spool/cron and similar), and restrict use of crontab installation utilities so only trusted users can install crontabs.
- Operational
Audit all existing crontab files for long or suspicious MAILTO lines and remove or shorten any overly long MAILTO values; remove untrusted or unexpected crontab entries created by local users.
Event History
Frequently Asked Questions
What is the severity of CVE-1999-0872?
CVE-1999-0872 is considered a high severity vulnerability due to the potential for local users to gain root access.
How do I fix CVE-1999-0872?
To fix CVE-1999-0872, you should update Vixie cron to a version that addresses the buffer overflow issue.
Who is affected by CVE-1999-0872?
CVE-1999-0872 affects local users on systems running vulnerable versions of Vixie cron, including specific releases of Debian, Red Hat, and SCO OpenLinux.
What type of vulnerability is CVE-1999-0872?
CVE-1999-0872 is a buffer overflow vulnerability that exploits the MAILTO environment variable in crontab files.
Can CVE-1999-0872 be exploited remotely?
CVE-1999-0872 cannot be exploited remotely, as it requires local user access to the system to be effective.