undici is vulnerable to Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| undici | undici | unaffected |
|
Configuration 1 [-]
|
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Undici | Undici |
|
Vendor Workaround
If upgrading is not immediately possible: * Validate header names: Ensure no duplicate Content-Length headers (case-insensitive) are present before passing headers to undici * Use object format: Pass headers as a plain object ({ 'content-length': '123' }) rather than an array, which naturally deduplicates by key * Sanitize user input: If headers originate from user input, normalize header names to lowercase and reject duplicates
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-2mjp-6q6p-2qxm | Undici has an HTTP Request/Response Smuggling issue |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.560% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Nodejs
Nodejs undici |
|
| CPEs | cpe:2.3:a:nodejs:undici:*:*:*:*:*:node.js:*:* | |
| Vendors & Products |
Nodejs
Nodejs undici |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Undici
Undici undici |
|
| Vendors & Products |
Undici
Undici undici |
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Undici allows duplicate HTTP Content-Length headers when they are provided in an array with case-variant names (e.g., Content-Length and content-length). This produces malformed HTTP/1.1 requests with multiple conflicting Content-Length values on the wire. Who is impacted: * Applications using undici.request(), undici.Client, or similar low-level APIs with headers passed as flat arrays * Applications that accept user-controlled header names without case-normalization Potential consequences: * Denial of Service: Strict HTTP parsers (proxies, servers) will reject requests with duplicate Content-Length headers (400 Bad Request) * HTTP Request Smuggling: In deployments where an intermediary and backend interpret duplicate headers inconsistently (e.g., one uses the first value, the other uses the last), this can enable request smuggling attacks leading to ACL bypass, cache poisoning, or credential hijacking | |
| Title | undici is vulnerable to Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') | |
| Weaknesses | CWE-444 | |
| References |
| |
| Metrics |
cvssV3_1
|