Message-header injection via unchecked CRLF
Published Feb 27, 2024 · Updated May 6, 2025
Header injection in Apache James Mime4J 0.8.9 and earlier allows remote attackers to add unintended headers to composed MIME messages. The RawField constructor accepts unencoded CRLF sequences in a header body, so the DOM message writer serializes attacker-controlled text as a separate header. Exploitation requires a consuming application to pass attacker-controlled header content to the DOM composition API; parsing MIME messages alone does not expose the flaw.
Summary
What happened
Header injection in Apache James Mime4J 0.8.9 and earlier allows remote attackers to add unintended headers to composed MIME messages. The RawField constructor accepts unencoded CRLF sequences in a header body, so the DOM message writer serializes attacker-controlled text as a separate header. Exploitation requires a consuming application to pass attacker-controlled header content to the DOM composition API; parsing MIME messages alone does not expose the flaw.
The record
- CVE
- CVE-2024-21742
- Published
- Feb 27, 2024
- Updated
- May 6, 2025
- Vendor
- The Apache Software Foundation
- Product
- Apache James Mime4J
- Classifications
- CWE-74, CWE-20
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 27, 2024CVE publishedPublication date reported by the CVE source.
- May 6, 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=0 <=0.8.9
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