CVE-2018-7159
MEDIUMEPSS 88th pctlDescription
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.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Exploit Intelligence
Elevated risk: more likely to be exploited than 88% of all known CVEs.
References
Related Vulnerabilities
Other CWE-115 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2020-27846 | Critical | 9.8 | 4.9% | - | Fix |
| CVE-2018-12116 | High | 7.5 | 4.6% | - | Fix |
| CVE-2018-12123 | Medium | 4.3 | 4.0% | - | Fix |
| CVE-2020-29509 | Medium | 5.6 | 2.1% | - | Fix |
| CVE-2020-29510 | Critical | 9.8 | 2.0% | - | - |
| CVE-2020-29511 | Medium | 5.6 | 1.9% | - | Fix |
Common questions
How do I fix CVE-2018-7159?
Published advisories record a fix for 3 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2018-7159 being actively exploited?
Not that we know of. CVE-2018-7159 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 3.6% is the estimated probability that it will be exploited in the next 30 days. That is higher than 88% of all scored CVEs.
How severe is CVE-2018-7159?
CVE-2018-7159 has a CVSS v3 base score of 5.3, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2018-7159 affect?
Published advisories record a fix for nodejs (Debian), Node.js (Windows application), Node.js (LTS) (Windows application). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2018-7159
Markdown
[](https://tridentstack.com/cve/CVE-2018-7159)HTML
<a href="https://tridentstack.com/cve/CVE-2018-7159"><img src="https://tridentstack.com/cve/badge/CVE-2018-7159.svg" alt="CVE-2018-7159"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2024-11-21.