CVE-2014-2957 json
The dmarc_process function in dmarc.c in Exim before 4.82.1, when EXPERIMENTAL_DMARC is enabled, allows remote attackers to execute arbitra…
published 2014-09-04 12 y ago modified 2026-06-17 4 mo ago also EUVD-2014-2979
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 5.3%
- EPSS 5.3% chance of exploitation in 30 days, percentile 92%
- public exploits
- 0
- none known
Summary
The dmarc_process function in dmarc.c in Exim before 4.82.1, when EXPERIMENTAL_DMARC is enabled, allows remote attackers to execute arbitrary code via the From header in an email, which is passed to the expand_string function.
Patch / fix
- exim4 Debian 14, Debian 13, Debian 12 4.82.1-1
debian advisories DEBIAN-CVE-2014-2957
- exim openSUSE Tumbleweed 4.86.2-2.2
opensuse advisories openSUSE-SU-2024:10017-1
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-2014-2957 updated cvss 7.5
exim: remote arbitrary code execution via DMARC code parsing
-
Red Hat Enterprise Linux 5 eximnot affected: vulnerable code not present
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
5.29% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
lists.exim.org
/lurker/message/20140528.122536.a31d60a4.en.html
mailing-list, patch, vendor-advisory
- git.exim.org /exim.git/commitdiff/5b7a7c051c9ab9ee7c924a611f90ef2be03e0ad0
-
openwall.com
/lists/oss-security/2021/05/04/7
mailing-list
Sources
- CVE List CVE-2014-2957
- NVD CVE-2014-2957
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.