LiveActive security incident?Get immediate response
CVE Record

CVE-2022-32215: The llhttp parser <v14.20.1, <v16.17.1 and <v18.9.1 in the http module in Node.js does not correctly handle...

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

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-32215 is a Node.js HTTP parsing flaw. Certain Node versions mishandle multi-line Transfer-Encoding headers, which can enable HTTP request smuggling. For exposed web services, this can let one request be interpreted differently by front-end and back-end systems, risking unauthorized routing or security-control bypass.

Executive priority

Treat this as high priority for public-facing Node.js applications because request smuggling can bypass perimeter assumptions. Urgency is lower where Node is fully upgraded or not exposed to untrusted HTTP traffic.

Technical view

The issue is in Node.js llhttp parsing within the http module before v14.20.1, v16.17.1, and v18.9.1. It is classified as CWE-444, inconsistent HTTP message interpretation. The source bundle does not provide CVSS data, exploit details, or proof of active exploitation.

Likely exposure

Most relevant exposure is internet-facing Node.js services using affected runtimes, especially behind reverse proxies, load balancers, or gateways that may parse HTTP differently.

Exploitation context

The bundle cites a HackerOne report and vendor advisories, but KEV is false and no provided source confirms active exploitation in the wild.

Researcher notes

Evidence supports parser-level HTTP request smuggling from multi-line Transfer-Encoding handling. The bundle lacks CVSS, exploitation telemetry, and detailed affected downstream product scope, so validation should focus on runtime versions and front-end/back-end HTTP parsing boundaries.

Mitigation direction

  • Upgrade affected Node.js 14, 16, and 18 deployments to fixed or later releases.
  • Apply distribution packages from Fedora, Debian, or relevant vendor advisories where Node is bundled.
  • Check Siemens guidance if using products covered by SSA-332410.
  • Review proxy and gateway normalization settings against vendor guidance.
  • Prioritize externally reachable services and shared hosting paths first.

Validation and detection

  • Inventory Node.js runtime versions across production, containers, CI images, and base images.
  • Confirm no deployed runtime is below v14.20.1, v16.17.1, or v18.9.1.
  • Identify services using Node's http module or frameworks built on it.
  • Map exposed Node services behind reverse proxies or load balancers.
  • Review logs for unexplained routing anomalies, malformed headers, or desynchronization symptoms.
Prepared
Confidence
high
Sources
9

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-444: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-32215 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
8Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
NodeJSNode4.0, 5.0, 6.0, 7.0, 8.0, 9.0, 10.0, 11.0, 12.0, 13.0, 14.0, 15.0, 16.0, 17.0, 18.0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-444 · source CWE mapping

Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')

Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.