HTTP desynchronization via unneutralized backend headers
Published Apr 4, 2024 · Updated Nov 12, 2024
HTTP response splitting in Apache HTTP Server 2.4.0 through 2.4.58 allows remote attackers to desynchronize HTTP connections. The affected response-processing modules pass backend-generated header values without neutralizing CRLF delimiters; Apache has not named the modules or functions. Exploitation requires a backend that accepts injected response headers and a victim request sharing the desynchronized connection.
Summary
What happened
HTTP response splitting in Apache HTTP Server 2.4.0 through 2.4.58 allows remote attackers to desynchronize HTTP connections. The affected response-processing modules pass backend-generated header values without neutralizing CRLF delimiters; Apache has not named the modules or functions. Exploitation requires a backend that accepts injected response headers and a victim request sharing the desynchronized connection.
The record
- CVE
- CVE-2024-24795
- Published
- Apr 4, 2024
- Updated
- Nov 12, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache HTTP Server
- Classifications
- CWE-113, CAPEC-34, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 4, 2024CVE publishedPublication date reported by the CVE source.
- Nov 12, 2024Record 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.58
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