Remote code execution via malformed PROXY addresses
Published May 3, 2024 · Updated Nov 3, 2025
Memory corruption in Exim before 4.96.2 allows remote attackers to execute code through crafted PROXY protocol address data. The SMTP receiver relies on string_is_ip_address() to validate proxy-supplied addresses, but the pre-fix parser fails to reject malformed special-element input. Reachability requires Exim to trust an untrusted PROXY protocol proxy; ordinary direct SMTP clients cannot reach the flawed path.
Summary
What happened
Memory corruption in Exim before 4.96.2 allows remote attackers to execute code through crafted PROXY protocol address data. The SMTP receiver relies on string_is_ip_address() to validate proxy-supplied addresses, but the pre-fix parser fails to reject malformed special-element input. Reachability requires Exim to trust an untrusted PROXY protocol proxy; ordinary direct SMTP clients cannot reach the flawed path.
The record
- CVE
- CVE-2023-42117
- Published
- May 3, 2024
- Updated
- Nov 3, 2025
- Vendor
- LibSPF2 Project
- Product
- Exim
- Classifications
- CWE-138, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 3, 2024CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=-
- Affected versionversion=4.96-RC1-11-315206fbf
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo