Response content injection via unsanitized header values
Published Sep 29, 2023 · Updated Sep 23, 2024
HTTP response splitting in ithewei libhv 1.3.2 and earlier allows remote attackers to inject headers and response bodies. HttpResponse header serialization emits CR and LF characters from untrusted header values without neutralizing message delimiters. Exploitation requires a consuming application to place attacker-controlled data in a response header; the injected body can execute script when a browser renders it.
Summary
What happened
HTTP response splitting in ithewei libhv 1.3.2 and earlier allows remote attackers to inject headers and response bodies. HttpResponse header serialization emits CR and LF characters from untrusted header values without neutralizing message delimiters. Exploitation requires a consuming application to place attacker-controlled data in a response header; the injected body can execute script when a browser renders it.
The record
- CVE
- CVE-2023-26147
- Published
- Sep 29, 2023
- Updated
- Sep 23, 2024
- Vendor
- ithewei
- Product
- libhv
- Classifications
- CWE-79, CWE-113, CAPEC-34, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 29, 2023CVE publishedPublication date reported by the CVE source.
- Sep 23, 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=0 <*
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
- HTTP Response Splitting in libhv 1.3.0 proof of conceptfunctional · demonstrated
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