CVE-2018-7159
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network without logging in. Limited direct impact.
- Exploit odds
- 3.5% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 3.5% in the next 30 days (EPSS).
- Severity: 5.3 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 3.5% · EPSS, next 30 days
- Weakness
- CWE-115
- Record status
- Modified
Affected
- Nodejs node.js ≤ 4.1.2
- Nodejs node.js < 4.9.0
- Nodejs node.js ≤ 6.8.1
- Nodejs node.js < 6.14.0
- Nodejs node.js ≤ 8.8.1
- Nodejs node.js < 8.11.0
- Nodejs node.js < 9.10.0
Attack profile CVSS 3.1 · 5.3
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2018-7159.md and follow it. Check whether this project is affected by CVE-2018-7159. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://nodejs.org/en/blog/vulnerability/march-2018-security-releases/
- https://nodejs.org/en/blog/vulnerability/march-2018-security-releases/
References
- https://access.redhat.com/errata/RHSA-2019:2258
- https://nodejs.org/en/blog/vulnerability/march-2018-security-releases/
- https://support.f5.com/csp/article/K27228191?utm_source=f5support&%3Butm_medium=RSS
- https://access.redhat.com/errata/RHSA-2019:2258
- https://nodejs.org/en/blog/vulnerability/march-2018-security-releases/
- https://support.f5.com/csp/article/K27228191?utm_source=f5support&%3Butm_medium=RSS