Client crash via invalid RFC 2047 decoding
Published Sep 9, 2023 · Updated Jul 25, 2026
Null-pointer dereference in Mutt after 1.5.2 and before 2.2.12 allows remote attackers to crash the client via a crafted email header. The RFC 2047 Base64 decoder accepts illegal characters and can reduce an entire header field to an empty result, violating downstream nonempty-header assumptions. The recipient must view the crafted message; the resulting null dereference interrupts that client process without reported data disclosure or modification.
Summary
What happened
Null-pointer dereference in Mutt after 1.5.2 and before 2.2.12 allows remote attackers to crash the client via a crafted email header. The RFC 2047 Base64 decoder accepts illegal characters and can reduce an entire header field to an empty result, violating downstream nonempty-header assumptions. The recipient must view the crafted message; the resulting null dereference interrupts that client process without reported data disclosure or modification.
The record
- CVE
- CVE-2023-4874
- Published
- Sep 9, 2023
- Updated
- Jul 25, 2026
- Vendor
- Mutt
- Product
- Mutt
- Classifications
- CWE-476, CWE-475
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 9, 2023CVE publishedPublication date reported by the CVE source.
- Jul 25, 2026Record 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=1.5.2 <2.2.12
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