Skip to content
CTI Academy Sponsor CTI Academy
HIGH · CVSS 7.8 CISA Known Exploited Vulnerability

CVE-2010-4345

Exim Privilege Escalation Vulnerability

Exim Exim

Exim 4.72 and earlier allows local users to gain privileges by leveraging the ability of the exim user account to specify an alternate configuration file with a directive that contains arbitrary commands, as demonstrated by the spool_directory directive.

CVSS
7.8
HIGH
EPSS
18%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
14 Dec 2010
CWE-77

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 25 March 2022. US federal agencies were required to remediate it by 15 April 2022.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 18%, which is higher than 97.2% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Frequently asked questions

Is CVE-2010-4345 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2010-4345.

What does CVE-2010-4345 affect?

CVE-2010-4345 affects Exim Exim. Exim 4.72 and earlier allows local users to gain privileges by leveraging the ability of the exim user account to specify an alternate configuration file with a directive that contains arbitrary commands, as demonstrated by the spool_directory directive.

How severe is CVE-2010-4345?

CVE-2010-4345 is rated HIGH with a CVSS base score of 7.8. EPSS puts the probability of exploitation in the next 30 days at 18%, higher than 97.2% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 15 April 2022.

How should organisations respond to CVE-2010-4345?

Apply the vendor patch for Exim Exim as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.