HTTP message splitting via unsanitized fields
Published Sep 21, 2021 · Updated Aug 4, 2024
Improper input validation in http4s 0.21.28 and earlier allows remote attackers to alter HTTP messages via crafted header or URI fields. Header names, values, status reason phrases, URI paths, and registered names accept carriage-return, newline, or null characters that affected backends render as delimiters, enabling response or request splitting. Exploitation requires an application to place attacker-controlled data in those fields and use an affected backend; the impact is message integrity compromise rather than direct code execution.
Summary
What happened
Improper input validation in http4s 0.21.28 and earlier allows remote attackers to alter HTTP messages via crafted header or URI fields. Header names, values, status reason phrases, URI paths, and registered names accept carriage-return, newline, or null characters that affected backends render as delimiters, enabling response or request splitting. Exploitation requires an application to place attacker-controlled data in those fields and use an affected backend; the impact is message integrity compromise rather than direct code execution.
The record
- CVE
- CVE-2021-41084
- Published
- Sep 21, 2021
- Updated
- Aug 4, 2024
- Vendor
- http4s
- Product
- http4s
- Classifications
- CWE-74, CWE-918, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 21, 2021CVE 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=<= 0.21.28
- Affected versionversion=>= 0.22.0, < 0.22.5
- Affected versionversion=>= 0.23.0, < 0.23.4
- Affected versionversion=>= 1.0.0-M1, < 1.0.0-M27
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