The HTTP parser in all current versions of Node.js ignores spaces in the `Content-Length` header, allowing input such as `Content-Length: 1
The HTTP parser in all current versions of Node.js ignores spaces in the `Content-Length` header, allowing input such as `Content-Length: 1 2` to be interpreted as having a value of `12`. The HTTP specification does not allow for spaces in the `Content-Length` value and the Node.js HTTP parser has been brought into line on this particular difference. The security risk of this flaw to Node.js users is considered to be VERY LOW as it is difficult, and may be impossible, to craft an attack that makes use of this flaw in a way that could not already be achieved by supplying an incorrect value for `Content-Length`. Vulnerabilities may exist in user-code that make incorrect assumptions about the potential accuracy of this value compared to the actual length of the data supplied. Node.js users crafting lower-level HTTP utilities are advised to re-check the length of any input supplied after parsing is complete.
- Published
- May 17, 2018
- Updated
- Jun 16, 2026
- EPSS
- 3.6% · 89th percentile
- CWE
- CWE-115
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.6%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| nodejs | node.js | cpe:2.3:a:nodejs:node.js |
Using node.js? Add it to your stack and be the first to know about CVEs like this one. (Node.js)
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- nodejs node.js4.0.0 and later · up to 4.1.2 inclusive
- nodejs node.js4.2.0 and later · before 4.9.0
- nodejs node.js6.0.0 and later · up to 6.8.1 inclusive
- nodejs node.js6.9.0 and later · before 6.14.0
- nodejs node.js8.0.0 and later · up to 8.8.1 inclusive
- nodejs node.js8.9.0 and later · before 8.11.0
- nodejs node.js9.0.0 and later · before 9.10.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (nodejs). Independent of NVD's CPE analysis and usually ahead of it.
The Node.js Project Node.js
- 4.x, 6.x, 8.x, 9.xaffected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | nodejs | before 8.11.0-r0 | 8.11.0-r0 |
| Debian:12 | nodejs | before 8.11.1~dfsg-2 | 8.11.1~dfsg-2 |
| Red Hat:enterprise_linux:7::client | http-parser | before 0:2.7.1-8.el7 | 0:2.7.1-8.el7 |
| Red Hat:enterprise_linux:7::client | http-parser-debuginfo | before 0:2.7.1-8.el7 | 0:2.7.1-8.el7 |
| Red Hat:enterprise_linux:7::client | http-parser-devel | before 0:2.7.1-8.el7 | 0:2.7.1-8.el7 |
| Red Hat:rhel_software_collections:3::el7 | rh-nodejs8-nodejs | before 0:8.11.4-1.el7 | 0:8.11.4-1.el7 |
| Red Hat:rhel_software_collections:3::el7 | rh-nodejs8-nodejs-debuginfo | before 0:8.11.4-1.el7 | 0:8.11.4-1.el7 |
| Red Hat:rhel_software_collections:3::el7 | rh-nodejs8-nodejs-devel | before 0:8.11.4-1.el7 | 0:8.11.4-1.el7 |
| Red Hat:rhel_software_collections:3::el7 | rh-nodejs8-nodejs-docs | before 0:8.11.4-1.el7 | 0:8.11.4-1.el7 |
| Red Hat:rhel_software_collections:3::el7 | rh-nodejs8-npm | before 0:5.6.0-8.11.4.1.el7 | 0:5.6.0-8.11.4.1.el7 |
| SUSE:Linux Enterprise Module for Web and Scripting 12 | nodejs4 | before 4.9.1-15.11.1 | 4.9.1-15.11.1 |
| SUSE:OpenStack Cloud 7 | nodejs6 | before 6.14.1-11.12.1 | 6.14.1-11.12.1 |
Same product
nodejs: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-15605HTTP request smuggling in Node.js 10, 12, and 13 causes malicious payload delivery when transfer-encoding is malformed56Plan
- CVE-2021-22883Node.js before 10.24.0, 12.21.0, 14.16.0, and 15.10.0 is vulnerable to a denial of service attack when too many connection attempts with an 52Plan
- CVE-2021-22930Node.js before 16.6.0, 14.17.4, and 12.22.4 is vulnerable to a use after free attack where an attacker might be able to exploit the memory c50Plan
- CVE-2021-22931Node.js before 16.6.0, 14.17.4, and 12.22.4 is vulnerable to Remote Code Execution, XSS, Application crashes due to missing input validation46Plan
- CVE-2020-8277A Node.js application that allows an attacker to trigger a DNS request for a host of their choice could trigger a Denial of Service in versi46Plan
- CVE-2017-14849Node.js 8.5.0 before 8.6.0 allows remote attackers to access unintended files, because a change to ".." handling was incompatible with the p46Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:nodejs | 8.11.0-r0 · Alpine:v3.10 | Package registry (OSV) |
| debian:nodejs | 8.11.1~dfsg-2 · Debian:12 | Package registry (OSV) |
| red hat:http-parser | 0:2.7.1-8.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:http-parser-debuginfo | 0:2.7.1-8.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:http-parser-devel | 0:2.7.1-8.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:rh-nodejs8-nodejs | 0:8.11.4-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-nodejs8-nodejs-debuginfo | 0:8.11.4-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-nodejs8-nodejs-devel | 0:8.11.4-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-nodejs8-nodejs-docs | 0:8.11.4-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-nodejs8-npm | 0:5.6.0-8.11.4.1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| suse:nodejs4 | 4.9.1-15.11.1 · SUSE:Linux Enterprise Module for Web and Scripting 12 | Package registry (OSV) |
| suse:nodejs6 | 6.14.1-11.12.1 · SUSE:OpenStack Cloud 7 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-115 · Misinterpretation of InputCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- access.redhat.com/errata/RHSA-2019:2258
- nodejs.org/en/blog/vulnerability/march-2018-security-releases/
- support.f5.com/csp/article/K27228191?utm_source=f5support&%3Butm_medium=RSS
Vendor advisories and official records. Exploit/PoC links are deliberately left out.