Skip to content
Fencer Intel
low 3.3

CVE-2010-0424 json

The edit_cmd function in crontab.c in (1) cronie before 1.4.4 and (2) Vixie cron (vixie-cron) allows local users to change the modification…

published 16y ago modified 4mo ago also EUVD-2010-0455

cvss
3.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 28%
public exploits
0
none known

Summary

The edit_cmd function in crontab.c in (1) cronie before 1.4.4 and (2) Vixie cron (vixie-cron) allows local users to change the modification times of arbitrary files, and consequently cause a denial of service, via a symlink attack on a temporary file in the /tmp directory.

Patch / fix

  • vixie-cron RHEL 5 4:4.1-81.el5

red hat advisories RHSA-2012:0304

  • cronie openSUSE Tumbleweed 1.5.0-65.4

opensuse advisories openSUSE-SU-2024:10139-1

Is CVE-2010-0424 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-2010-0424 updated cvss 3.6

cronie: Race condition by setting timestamp of user's crontab file, when editing the file

  • Red Hat Enterprise Linux 4 vixie-cron
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux 6 cronie, cronie-anacron, cronie-noanacron
    affected: no fix available
  • Red Hat Enterprise Linux (v. 5 server) vixie-cron 4.1-81.el5 Red Hat Enterprise Linux Desktop (v. 5 client) vixie-cron 4.1-81.el5
    fixed: vendor fix RHSA-2012:0304

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.35% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 3.3 AV:L/AC:M/Au:N/C:N/I:P/A:P

Classification

Weakness
  • CWE-59 Improper Link Resolution Before File Access

References

Sources

Fencer Intel 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.