CVE-2014-9116
NoneCVSS
—
EPSS
9.7%
Published
Dec 2, 2014
CISA due date
—
Cloudanix analysis
A specially formatted email can crash the program people use to read mail, stopping them from accessing their inbox until the program is fixed or restarted.
- Exploitation
- Remote Unauthenticated
- Attacker needs
- None
- Complexity
- Low
- Impact
- Denial Of Service
- Component
- Application
- Class
- Memory Corruption
- Remediation
- Upgrade
- Effort
- Medium
- Patch risk
- Low
What it actually does
Improper handling of a leading newline in an email header causes mutt_substrdup to perform an out-of-bounds read/write, resulting in a heap-based buffer overflow that crashes the process.
Why it matters to the business
Attackers can remotely crash the mail client on affected systems, producing immediate denial of service that disrupts email workflows and may require manual restarts or patching to restore service.
How an attack unfolds
An attacker crafts an email containing a header whose first character is a newline followed by an empty body and sends it to a victim using the vulnerable mutt client; when mutt parses the header the malformed input reaches write_one_header and mutt_substrdup, triggering the overflow and crash.
How to fix it
Upgrade mutt (and any dependent wordpress packages) to the versions listed in the fixed_versions field for each distribution; after upgrade, restart all mutt processes and verify the new binary no longer accepts the malformed header.
How to confirm the fix worked
Send a test message containing a leading-newline header to a lab instance running the patched mutt; confirm the client does not crash and that the version string matches the fixed release.
Typical attack path
- Craft a minimal RFC-compliant message whose first header line begins with a bare newline and has no body content.
- Deliver the message via SMTP or place it in a mailbox the victim will open with mutt.
- Victim’s mutt client parses the header, calling write_one_header then mutt_substrdup with attacker-controlled length.
- Heap buffer overflow occurs, process crashes, and email access is lost until restart.
How to detect it
Search mail-server and client logs for message deliveries that contain headers beginning with a literal newline; inspect any resulting crash dumps or segfault entries in system logs around the same timestamp.
- segfault.*mutt
- mutt_substrdup
- header with empty body
What your security team should do
- Immediately schedule patching of all Debian 11/12/13 wordpress and mutt packages to the versions containing 4.2.4+dfsg-1.
- Block or quarantine messages whose headers begin with a bare newline at the MTA if possible until patches are deployed.
- Add the supplied detection_iocs to SIEM rules and run historical searches for the past 90 days.
The record
The write_one_header function in mutt 1.5.23 does not properly handle newline characters at the beginning of a header, which allows remote attackers to cause a denial of service (crash) via a header with an empty body, which triggers a heap-based buffer overflow in the mutt_substrdup function.
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|---|---|---|
| Debian:11 | mutt | 0 | 1.5.23-2 |
| Debian:12 | mutt | 0 | 1.5.23-2 |
| Debian:13 | mutt | 0 | 1.5.23-2 |
| Debian:6.0 | mutt | 0 | 1.5.20-9+squeeze4 |
| Debian:7 | mutt | 0 | 1.5.21-6.2+deb7u3 |
| Mageia:4 | mutt | 0 | 1.5.23-1.mga4 |
| SUSE:Linux Enterprise Desktop 12 SP3 | mutt | 0 | 1.10.1-55.6.1 |
| SUSE:Linux Enterprise Desktop 12 SP3 | mutt | 0 | 1.10.1-55.3.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 | mutt | 0 | 1.10.1-3.3.4 |
| SUSE:Linux Enterprise Server 12 SP3 | mutt | 0 | 1.10.1-55.6.1 |
| SUSE:Linux Enterprise Server 12 SP3 | mutt | 0 | 1.10.1-55.3.1 |
| SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | mutt | 0 | 1.10.1-55.6.1 |
| SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | mutt | 0 | 1.10.1-55.3.1 |
| Ubuntu:14.04:LTS | mutt | 0 | 1.5.21-6.4ubuntu2.1 |
| openSUSE:Tumbleweed | mutt | 0 | 1.6.2-3.1 |
Related vulnerabilities
- CVE-2024-49394 In mutt and neomutt the In-Reply-To email header field is not protected by cryptographic… Also affects mutt
- CVE-2024-49395 In mutt and neomutt, PGP encryption does not use the --hidden-recipient mode which may… Also affects mutt
- CVE-2024-49393 In neomutt and mutt, the To and Cc email headers are not validated by cryptographic… Also affects mutt
- CVE-2026-43863 mutt before 2.3.2 has an infinite loop in data_object_to_stream in crypt-gpgme.c. Also affects mutt
- CVE-2026-43859 mutt before 2.3.2 sometimes uses strfcpy instead of memcpy for the IMAP auth_cram MD5… Also affects mutt
- CVE-2026-43862 In mutt before 2.3.2, the imap_auth_gss security level is mishandled. Also affects mutt
- CVE-2026-43861 mutt before 2.3.2 does not check for '\0' in url_pct_decode. Also affects mutt
- CVE-2026-112108 A vulnerability was determined in ztxz16 fastllm up to 0.1.8.2. CWE-119