Response splitting via unsafe Content-Type header merging
Published Jul 10, 2025 · Updated Nov 4, 2025
HTTP response splitting in Apache HTTP Server 2.4.0 through 2.4.63 allows remote attackers to inject a second HTTP response. The ap_http_header_filter path in modules/http/http_filters.c merges attacker-controlled Content-Type values into outgoing headers without preserving a single response boundary. Exploitation requires control of a hosted or proxied application's Content-Type response header, allowing a downstream client or intermediary to interpret an injected response separately.
Summary
What happened
HTTP response splitting in Apache HTTP Server 2.4.0 through 2.4.63 allows remote attackers to inject a second HTTP response. The ap_http_header_filter path in modules/http/http_filters.c merges attacker-controlled Content-Type values into outgoing headers without preserving a single response boundary. Exploitation requires control of a hosted or proxied application's Content-Type response header, allowing a downstream client or intermediary to interpret an injected response separately.
The record
- CVE
- CVE-2024-42516
- Published
- Jul 10, 2025
- Updated
- Nov 4, 2025
- Vendor
- The Apache Software Foundation
- Product
- Apache HTTP Server
- Classifications
- CWE-20
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 10, 2025CVE publishedPublication date reported by the CVE source.
- Nov 4, 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=2.4.0 <=2.4.63
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