CVE-2022-32215CWE-444

CVE-2022-32215: vulnerability in NodeJS Node

Published · Updated

25Vexday Risk Score

No sign of exploitation. No public exploitation artifact known so far.

ssvc Trackepss 70%
exploitation probability
70%top 1% of all CVEs
observed exploitation
nono source reports it
What the vendors declare (VEX)

Official vendor statements in CSAF/VEX format: whether their product is affected, already fixed, or ruled out — and why. These are the vendor's assertions, not Vexday's judgment.

Fixed
5 products (144 components)
Red Hat Enterprise Linux AppStream (v. 8) · Red Hat Enterprise Linux AppStream (v. 9) · Red Hat Enterprise Linux AppStream EUS (v.8.4) · Red Hat Software Collections for RHEL Workstation(v. 7) · Red Hat Software Collections for RHEL(v. 7)
Not affected
4 products (20 components) — because the vulnerable code is not present in the product
Red Hat Enterprise Linux 8 · Red Hat Enterprise Linux AppStream (v. 9) · Red Hat Software Collections for RHEL Workstation(v. 7) · Red Hat Software Collections for RHEL(v. 7)
In short

Node.js's HTTP parser fails to properly process Transfer-Encoding headers that span multiple lines, allowing attackers to sneak hidden requests through proxies and firewalls by exploiting this misinterpretation.

Technical detail

The llhttp parser in Node.js versions before 14.20.1, 16.17.1, and 18.9.1 incorrectly parses multi-line Transfer-Encoding headers, enabling HTTP request smuggling attacks where an attacker sends a crafted request that is interpreted differently by frontend and backend servers, leading to request desynchronization and potential unauthorized access or cache poisoning.

Summary generated and translated by AI from the official description.
The llhttp parser <v14.20.1, <v16.17.1 and <v18.9.1 in the http module in Node.js does not correctly handle multi-line Transfer-Encoding headers. This can lead to HTTP Request Smuggling (HRS).
Affected products
NodeJS · Node