HTTP request injection via unvalidated Content-Type
Published Aug 13, 2022 · Updated Apr 22, 2025
CRLF injection in Undici 5.8.0 and earlier allows remote attackers to inject a second HTTP request through a crafted content-type value. The processHeader path appended the value to the serialized header block without rejecting CRLF characters, allowing the value to terminate the first request and introduce another. Exploitation requires an application to pass attacker-controlled text as the content-type header, and the demonstrated consequence is an unauthorized downstream request.
Summary
What happened
CRLF injection in Undici 5.8.0 and earlier allows remote attackers to inject a second HTTP request through a crafted content-type value. The processHeader path appended the value to the serialized header block without rejecting CRLF characters, allowing the value to terminate the first request and introduce another. Exploitation requires an application to pass attacker-controlled text as the content-type header, and the demonstrated consequence is an unauthorized downstream request.
The record
- CVE
- CVE-2022-35948
- Published
- Aug 13, 2022
- Updated
- Apr 22, 2025
- Vendor
- Node.js
- Product
- Undici
- Classifications
- CWE-93
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 13, 2022CVE publishedPublication date reported by the CVE source.
- Apr 22, 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==< 5.8.0
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
- GHSA content-type request-injection exampleproof of concept · 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