CVE-2018-7159

Medium

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.

SeverityMedium
CVSS5.3
Exploit probability—
ProductNodejs Node.js
PublishedMay 17, 2018
First seenMay 17, 2018
Weakness typeCWE-115CWE-115

How to fix

Update
  • nodejs node.js4.9.0, 6.14.0, 8.11.0, 9.10.0 or later

Affected products

ProductAffected versionsFixed in
nodejs node.js4.0.0 ≤ v ≤ 4.1.2, 4.2.0 ≤ v < 4.9.0, 6.0.0 ≤ v ≤ 6.8.1, 6.9.0 ≤ v < 6.14.0, 8.0.0 ≤ v ≤ 8.8.1, 8.9.0 ≤ v < 8.11.0, 9.0.0 ≤ v < 9.10.04.9.0, 6.14.0, 8.11.0, 9.10.0

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.