Improper Input Validation Affecting http-parser-devel package, versions <0:2.7.1-8.el7


Severity

Recommended
0.0
medium
0
10

Based on CentOS security rating.

Threat Intelligence

EPSS
0.13% (49th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Improper Input Validation vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-CENTOS7-HTTPPARSERDEVEL-2144465
  • published26 Jul 2021
  • disclosed8 Mar 2018

Introduced: 8 Mar 2018

CVE-2018-7159  (opens in a new tab)
CWE-20  (opens in a new tab)

How to fix?

Upgrade Centos:7 http-parser-devel to version 0:2.7.1-8.el7 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream http-parser-devel package and not the http-parser-devel package as distributed by Centos. See How to fix? for Centos:7 relevant fixed versions and status.

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.

CVSS Scores

version 3.1