CVE-2018-7159
Last modified
CVE-2018-7159 is a medium-severity vulnerability rated 5.3/10 on the CVSS scale. 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. EPSS estimates a 3.62% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Nodejs | Node.Js | >= 4.0.0, <= 4.1.2 |
| Nodejs | Node.Js | >= 4.2.0, < 4.9.0 |
| Nodejs | Node.Js | >= 6.0.0, <= 6.8.1 |
| Nodejs | Node.Js | >= 6.9.0, < 6.14.0 |
| Nodejs | Node.Js | >= 8.0.0, <= 8.8.1 |
| Nodejs | Node.Js | >= 8.9.0, < 8.11.0 |
| Nodejs | Node.Js | >= 9.0.0, < 9.10.0 |
References
- https://access.redhat.com/errata/RHSA-2019:2258Third Party Advisory
- https://access.redhat.com/errata/RHSA-2019:2258Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2018-7159?
How severe is CVE-2018-7159?
How do I fix CVE-2018-7159?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2018
- CVE-2018-7153Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultID…
- CVE-2018-7154Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultID…
- CVE-2018-7155Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultID…
- CVE-2018-7156Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultID…
- CVE-2018-7157Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultID…
- CVE-2018-7158The `'path'` module in the Node.js 4.x release line contains…7.5
- CVE-2018-7160The Node.js inspector, in 6.x and later is vulnerable to a D…8.8
- CVE-2018-7161All versions of Node.js 8.x, 9.x, and 10.x are vulnerable an…7.5
- CVE-2018-7162All versions of Node.js 9.x and 10.x are vulnerable and the …7.5
- CVE-2018-7164Node.js versions 9.7.0 and later and 10.x are vulnerable and…7.5
- CVE-2018-7166In all versions of Node.js 10 prior to 10.9.0, an argument p…7.5
- CVE-2018-7167Calling Buffer.fill() or Buffer.alloc() with some parameters…7.5
Are you affected by CVE-2018-7159?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
