dbcve.org
Node.jsApplication

CVE-2022-32212

HIGH · 8.1 CVSS v3.1 Published 2022-07-14
Fix available
A fix is available. Upgrade to 1.0 / 14.20.1 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Node.js versions prior to 14.20.0, 16.20.0, and 18.5.0 contain an OS command injection vulnerability in the IsAllowedHost check used for DNS rebinding protection. The IsIPAddress function fails to properly validate IP addresses before making DNS requests, allowing attackers to bypass the host allowlist through invalid IP addresses and conduct rebinding attacks that can lead to arbitrary command execution.

MitigationUpgrade Node.js to version 14.20.0 or later, 16.20.0 or later, or 18.5.0 or later. For applications using custom IsAllowedHost implementations, ensure proper IP address validation occurs before any DNS resolution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Node.jsApplication
Affected:>= 14.0.0, <= 14.14.0>= 14.15.0, < 14.20.1>= 16.0.0, <= 16.12.0>= 16.13.0, < 16.17.1>= 18.0.0, < 18.5.0
Debian LinuxOperating system
Affected:= 10.0= 11.0
FedoraOperating system
Affected:= 35= 36= 37
Sinec InsApplication
Affected:< 1.0= 1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Node.js installation and version
    Run 'node --version' to determine the installed Node.js version
    Affected if The version falls within any of these ranges: 14.0.0-14.14.0, 14.15.0-14.19.x (before 14.20.1), 16.0.0-16.12.0, 16.13.0-16.17.0 (before 16.17.1), or 18.0.0-18.4.x (before 18.5.0)
  2. Identify HTTP server usage with host allowlist
    Search application source code for usage of the --inspector-host flag, the inspector module, or any code implementing IsAllowedHost or IsIPAddress functions
    Affected if The application uses Node.js inspector or debugger functionality with host allowlist configuration
  3. Check for exposed debugger or inspector endpoints
    Review network configurations and application code for exposed inspector endpoints (typically port 9229) that accept host parameters
    Affected if An HTTP inspector or debugging endpoint is exposed and accessible to untrusted networks
  4. Review custom IsAllowedHost implementations
    Search codebase for custom implementations of host validation or DNS rebinding protection logic
    Affected if Custom IsAllowedHost code performs IP validation before DNS resolution and may be vulnerable to invalid IP bypass

You are affected if you run a vulnerable Node.js version AND your application exposes the inspector or debugging interface with host allowlist protection, particularly if custom IsAllowedHost implementations are in use.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.0 / 14.20.1 / 16.17.1 or later
Fixed in 1.014.20.116.17.1
Interim mitigation

Upgrade Node.js to version 14.20.0 or later, 16.20.0 or later, or 18.5.0 or later. For applications using custom IsAllowedHost implementations, ensure proper IP address validation occurs before any DNS resolution.

Recommended fix High confidence

Node.js 14.20.1+ / 16.17.1+ / 18.5.0+ (LTS recommended)

  1. 1. Identify the current Node.js version by running `node --version`
  2. 2. For Node.js 14.x installations: Upgrade to version 14.20.1 or later (e.g., 14.21.0 LTS)
  3. 3. For Node.js 16.x installations: Upgrade to version 16.17.1 or later (e.g., 16.20.0 LTS or 18.x LTS)
  4. 4. If using a package manager, update accordingly: `nvm install 14.20.1` or `nvm install 16.17.1` or `nvm install 18`
  5. 5. Verify the upgrade was successful by running `node --version`
  6. 6. Test that your application functions correctly with the new Node.js version
  7. 7. Ensure any environment-specific configurations (e.g., IsAllowedHost settings) are reviewed after upgrade
Caveat Minor or patch version upgrades typically have low risk; verify compatibility with your application's dependencies and any native modules

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Node.js Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-32212 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-32212 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data