HTTP response splitting via disabled header validation
Published Feb 19, 2020 · Updated Aug 4, 2024
HTTP response splitting in WSO2 transport-http before 6.3.1 allows remote attackers to inject additional HTTP responses via crafted headers. Util.createHttpResponse and createFullHttpResponse constructed Netty responses with header validation disabled, allowing CRLF characters in outbound header values. A consuming C5 application must place attacker-controlled data into a response header, and successful exploitation requires user interaction to alter downstream HTTP content.
Summary
What happened
HTTP response splitting in WSO2 transport-http before 6.3.1 allows remote attackers to inject additional HTTP responses via crafted headers. Util.createHttpResponse and createFullHttpResponse constructed Netty responses with header validation disabled, allowing CRLF characters in outbound header values. A consuming C5 application must place attacker-controlled data into a response header, and successful exploitation requires user interaction to alter downstream HTTP content.
The record
- CVE
- CVE-2019-10797
- Published
- Feb 19, 2020
- Updated
- Aug 4, 2024
- Vendor
- WSO2
- Product
- WSO2 transport-http
- Classifications
- CWE-113, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 19, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=All versions prior to version v6.3.1
What conditions does exploitation require?
What is affected?
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