CVE-2000-1096
First published: Tue Jan 09 2001(Updated: )
crontab by Paul Vixie uses predictable file names for a temporary file and does not properly ensure that the file is owned by the user executing the crontab -e command, which allows local users with write access to the crontab spool directory to execute arbitrary commands by creating world-writeable temporary files and modifying them while the victim is editing the file.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Vixie Cron | =3.0_pl1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2000-1096?
CVE-2000-1096 is considered a high severity vulnerability due to its ability to allow local users to execute arbitrary commands.
How do I fix CVE-2000-1096?
To fix CVE-2000-1096, consider updating Vixie cron to a version that addresses the file ownership issues.
Who is affected by CVE-2000-1096?
Local users with write access to the crontab spool directory on systems running vulnerable versions of Vixie cron are affected by CVE-2000-1096.
What component is vulnerable in CVE-2000-1096?
The vulnerability lies in the crontab command of Vixie cron version 3.0_pl1.
Can CVE-2000-1096 be exploited remotely?
CVE-2000-1096 cannot be exploited remotely, as it requires local access to the system.
- agent/type
- agent/first-publish-date
- agent/last-modified-date
- agent/severity
- agent/weakness
- agent/remedy
- agent/references
- agent/author
- agent/tags
- agent/softwarecombine
- agent/description
- agent/event
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/nvd-historical
- vendor/paul vixie
- canonical/vixie cron
- version/vixie cron/3.0_pl1