Skip to content
Fencer Intel
medium 4.4

CVE-2010-2024 json

transports/appendfile.c in Exim before 4.72, when MBX locking is enabled, allows local users to change permissions of arbitrary files or cr…

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

cvss
4.4
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 20%
public exploits
0
none known

Summary

transports/appendfile.c in Exim before 4.72, when MBX locking is enabled, allows local users to change permissions of arbitrary files or create arbitrary files, and cause a denial of service or possibly gain privileges, via a symlink attack on a lockfile in /tmp/.

Patch / fix

  • exim4 Debian 14, Debian 13, Debian 12 4.72-1

debian advisories DEBIAN-CVE-2010-2024

  • exim openSUSE Tumbleweed 4.86.2-2.2

opensuse advisories openSUSE-SU-2024:10017-1

Is CVE-2010-2024 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-2024 updated cvss 2.1

exim: race condition when MBX locking is enabled

  • Red Hat Enterprise Linux 4 exim Red Hat Enterprise Linux 5 exim
    affected: no fix available

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

CVSS scores

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

Classification

Weakness
  • CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization

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.