LiveActive security incident?Get immediate response
CVE Record

CVE-2022-32212: A OS Command Injection vulnerability exists in Node.js versions <14.20.0, <16.20.0, <18.5.0 due to an insuf...

A OS Command Injection vulnerability exists in Node.js versions <14.20.0, <16.20.0, <18.5.0 due to an insufficient IsAllowedHost check that can easily be bypassed because IsIPAddress does not properly check if an IP address is invalid before making DBS requests allowing rebinding attacks.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-32212 is an OS command injection issue in Node.js. The CVE states that affected Node.js versions before the named fixed releases can have a host allow-list check bypassed, enabling DNS rebinding attacks. Business risk depends on where affected Node.js runtimes are deployed and exposed.

Executive priority

Treat this as a targeted runtime upgrade priority rather than a confirmed emergency. The business concern is older Node.js deployments with exposure that could make DNS rebinding practical. Prioritize asset discovery and upgrades where Node.js is internet-facing or operationally sensitive.

Technical view

The CVE describes insufficient IsAllowedHost validation in Node.js. It says IsIPAddress did not properly reject invalid IP addresses before DNS requests, allowing the host check to be bypassed and enabling rebinding attacks. The source names fixed thresholds: 14.20.0, 16.20.0, and 18.5.0.

Likely exposure

Organizations running Node.js versions below 14.20.0, 16.20.0, or 18.5.0 may be exposed. The source bundle lists many older major versions, but provides no CVSS score, environmental prerequisites, or detailed product configuration scope.

Exploitation context

The bundle includes a public HackerOne reference and states DNS rebinding attacks are possible. It does not cite CISA KEV listing or active exploitation in the wild, so active exploitation should not be assumed from these sources.

Researcher notes

The provided evidence is limited: no CVSS, no exploit maturity details, and no configuration matrix. The key technical lead is the IsAllowedHost and IsIPAddress validation failure leading to DNS rebinding. Validate scope against official Node.js advisories before expanding affected assumptions.

Mitigation direction

  • Upgrade Node.js to the fixed version for the deployed major line or later.
  • Inventory systems running Node.js 4.x through 18.x, especially older maintained services.
  • Check Node.js vendor guidance for unsupported branches and migration direction.
  • Prioritize exposed services where host validation or DNS rebinding protections matter.

Validation and detection

  • Confirm exact Node.js runtime versions on servers, containers, build images, and developer tooling.
  • Compare deployed versions against 14.20.0, 16.20.0, and 18.5.0 thresholds.
  • Review exposure of services relying on Node.js host allow-list behavior.
  • Track remediation evidence through package manifests, images, and runtime version checks.
Prepared
Confidence
medium
Sources
3

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 · medium confidence lookup

CWE-284: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-32212 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
2Source 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-284 · source CWE mapping

Improper Access Control

Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.