CVE-2024-39929

Exp

Exim through 4.97.1 misparses a multiline RFC 2231 header filename, and thus remote attackers can bypass a $mime_filename extension-blocking protection mechanism, and potentially deliver executable attachments to the mailboxes of end users.

Published: 2024-07-04 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-39929 is rated High Exploit Risk (66.1/100): CVSS Medium severity, with high exploitation likelihood (EPSS 41.23%, 98th percentile). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2024-39929

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2024-39929

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 60.31% 41.23% -19.08%
2 2026-04-17 63.91% 60.31% -3.61%
3 2026-04-04 — 63.91% —

Full EPSS history (32 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-39929

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.4 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 2.5 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2024-39929

OS Trackers for CVE-2024-39929

vendor priority summary link
alpine — CVE-2024-39929: 1 source package rows (exim); 37 state rows across 4 repos (3.20-community, 3.21-community, 3.22-community, edge-community); fixed 4, open 33. https://security.alpinelinux.org/vuln/CVE-2024-39929
debian not yet assigned CVE-2024-39929 not yet assigned priority: Debian including 1 source packages (exim4), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2024-39929
redhat high — https://access.redhat.com/security/cve/CVE-2024-39929
ubuntu medium CVE-2024-39929 medium priority: Ubuntu including 1 source packages (exim4), 8 status rows across 8 suites (bionic, focal, jammy, mantic, noble, trusty, upstream, xenial): released 5, ignored 1, needs-triage 1, not-affected 1. https://ubuntu.com/security/CVE-2024-39929

Affected software / configurations for CVE-2024-39929

Vendor Product Version Raw CPE
exim exim <= 4.97.1 cpe:2.3:a:exim:exim:*:*:*:*:*:*:*:*

References for CVE-2024-39929

cvelogic Threat Intelligence