CVE-2018-7159 Detail

Current 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.


Source: 
MITRE

View Analysis Description

Analysis 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.


Source: 
MITRE



Severity


CVSS 3.x Severity and Metrics:

References to Advisories, Solutions, and Tools


By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because
they may have information that would be of interest to you. No inferences should be drawn on account of other sites
being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose.
NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further,
NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about
this page to nvd@nist.gov.

Weakness Enumeration






CWE-ID CWE Name Source
CWE-20 Improper Input Validation

NIST  
CWE-115 Misinterpretation of Input

Node.js  

Known Affected Software Configurations
Switch to CPE 2.2


Configuration 1 ( hide )

 cpe:2.3:a:nodejs:node.js:*:*:*:*:-:*:*:*
     Show Matching CPE(s)
From (including)
4.0.0
Up to (including)
4.1.2
 cpe:2.3:a:nodejs:node.js:*:*:*:*:lts:*:*:*
     Show Matching CPE(s)
From (including)
4.2.0
Up to (excluding)
4.9.0
 cpe:2.3:a:nodejs:node.js:*:*:*:*:-:*:*:*
     Show Matching CPE(s)
From (including)
6.0.0
Up to (including)
6.8.1
 cpe:2.3:a:nodejs:node.js:*:*:*:*:lts:*:*:*
     Show Matching CPE(s)
From (including)
6.9.0
Up to (excluding)
6.14.0
 cpe:2.3:a:nodejs:node.js:*:*:*:*:-:*:*:*
     Show Matching CPE(s)
From (including)
8.0.0
Up to (including)
8.8.1
 cpe:2.3:a:nodejs:node.js:*:*:*:*:lts:*:*:*
     Show Matching CPE(s)
From (including)
8.9.0
Up to (excluding)
8.11.0
 cpe:2.3:a:nodejs:node.js:*:*:*:*:-:*:*:*
     Show Matching CPE(s)
From (including)
9.0.0
Up to (excluding)
9.10.0

Change History


4 change records found
show changes

Quick Info

CVE Dictionary Entry:
CVE-2018-7159
NVD Published Date:
05/17/2018
NVD Last Modified:
02/13/2020










Source link

Write a comment:
*

Your email address will not be published.