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 insufficient IsAllowedHost check that
Noroxi assessment
Priority: Monitor (action score 34/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 6.4% (FIRST EPSS); higher than 93.6% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: NodeJS Node 10.*, 11.*, 12.*.
- Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to NodeJS Node 10.*, 11.*, 12.* or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- BDU:2024-07321
- ALSA-2022:6448
- ALSA-2022:6595
- DLA-3137-1
- DSA-5326-1
- openSUSE-SU-2024:12199-1
- openSUSE-SU-2024:12349-1
- RHSA-2022:6389
- RHSA-2022:6448
- RHSA-2022:6449
- RHSA-2022:6595
- RHSA-2022:6985
- RLSA-2022:6448
- RLSA-2022:6449
- RLSA-2022:6595
- SUSE-SU-2022:2415-1
- SUSE-SU-2022:2416-1
- SUSE-SU-2022:2417-1
- SUSE-SU-2022:2425-1
- SUSE-SU-2022:2430-1
- Published
- Jul 14, 2022
- Updated
- Jun 17, 2026
- EPSS
- 6.4% · 93th percentile
- CWE
- CWE-284
Report tools
Action score
34
Monitor
Low priority for now.
- CVSS
- 32 / 40 · 8.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 2 / 30 · 6.4%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| nodejs | node.js | cpe:2.3:a:nodejs:node.js |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
| siemens | sinec ins | cpe:2.3:a:siemens:sinec_ins |
Using node.js? Add it to your stack and be the first to know about CVEs like this one. (Node.js)
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- nodejs node.js14.0.0 and later · up to 14.14.0 inclusive
- nodejs node.js14.15.0 and later · before 14.20.1
- nodejs node.js16.0.0 and later · up to 16.12.0 inclusive
- nodejs node.js16.13.0 and later · before 16.17.1
- nodejs node.js18.0.0 and later · before 18.5.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (hackerone). Independent of NVD's CPE analysis and usually ahead of it.
NodeJS Node
- 4.0 and later · before 4.*affected · semver
- 5.0 and later · before 5.*affected · semver
- 6.0 and later · before 6.*affected · semver
- 7.0 and later · before 7.*affected · semver
- 8.0 and later · before 8.*affected · semver
- 9.0 and later · before 9.*affected · semver
- 10.0 and later · before 10.*affected · semver
- 11.0 and later · before 11.*affected · semver
- 12.0 and later · before 12.*affected · semver
- 13.0 and later · before 13.*affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | nodejs | before 1:14.20.0-2.module_el8.6.0+3261+490666b3 | 1:14.20.0-2.module_el8.6.0+3261+490666b3 |
| AlmaLinux:8 | nodejs-devel | before 1:14.20.0-2.module_el8.6.0+3261+490666b3 | 1:14.20.0-2.module_el8.6.0+3261+490666b3 |
| AlmaLinux:8 | nodejs-docs | before 1:14.20.0-2.module_el8.6.0+3261+490666b3 | 1:14.20.0-2.module_el8.6.0+3261+490666b3 |
| AlmaLinux:8 | nodejs-full-i18n | before 1:14.20.0-2.module_el8.6.0+3261+490666b3 | 1:14.20.0-2.module_el8.6.0+3261+490666b3 |
| AlmaLinux:8 | nodejs-nodemon | before 2.0.19-2.module_el8.6.0+3261+490666b3 | 2.0.19-2.module_el8.6.0+3261+490666b3 |
| AlmaLinux:8 | nodejs-packaging | before 23-3.module_el8.5.0+2618+8d46dafd | 23-3.module_el8.5.0+2618+8d46dafd |
| AlmaLinux:8 | npm | before 1:6.14.17-1.14.20.0.2.module_el8.6.0+3261+490666b3 | 1:6.14.17-1.14.20.0.2.module_el8.6.0+3261+490666b3 |
| AlmaLinux:9 | nodejs | before 1:16.16.0-1.el9_0 | 1:16.16.0-1.el9_0 |
| AlmaLinux:9 | nodejs-docs | before 1:16.16.0-1.el9_0 | 1:16.16.0-1.el9_0 |
| AlmaLinux:9 | nodejs-full-i18n | before 1:16.16.0-1.el9_0 | 1:16.16.0-1.el9_0 |
| AlmaLinux:9 | nodejs-libs | before 1:16.16.0-1.el9_0 | 1:16.16.0-1.el9_0 |
| AlmaLinux:9 | nodejs-nodemon | before 2.0.19-1.el9_0 | 2.0.19-1.el9_0 |
| AlmaLinux:9 | npm | before 1:8.11.0-1.16.16.0.1.el9_0 | 1:8.11.0-1.16.16.0.1.el9_0 |
| Debian:10 | nodejs | before 10.24.0~dfsg-1~deb10u2 | 10.24.0~dfsg-1~deb10u2 |
| Debian:11 | nodejs | before 12.22.12~dfsg-1~deb11u3 | 12.22.12~dfsg-1~deb11u3 |
| Debian:12 | nodejs | before 18.6.0+dfsg-3 | 18.6.0+dfsg-3 |
| openSUSE:Leap 15.3 | nodejs10 | before 10.24.1-150000.1.47.1 | 10.24.1-150000.1.47.1 |
| openSUSE:Leap 15.3 | nodejs12 | before 12.22.12-150200.4.35.1 | 12.22.12-150200.4.35.1 |
| openSUSE:Leap 15.3 | nodejs14 | before 14.20.0-150200.15.34.1 | 14.20.0-150200.15.34.1 |
| openSUSE:Leap 15.3 | nodejs16 | before 16.16.0-150300.7.6.2 | 16.16.0-150300.7.6.2 |
| openSUSE:Leap 15.4 | nodejs16 | before 16.16.0-150400.3.3.2 | 16.16.0-150400.3.3.2 |
| openSUSE:Leap 15.4 | nodejs18 | before 18.13.0-150400.9.3.1 | 18.13.0-150400.9.3.1 |
| openSUSE:Tumbleweed | nodejs16 | before 16.16.0-1.1 | 16.16.0-1.1 |
| openSUSE:Tumbleweed | nodejs18 | before 18.9.0-1.1 | 18.9.0-1.1 |
+61
Same product
nodejs: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-15605HTTP request smuggling in Node.js 10, 12, and 13 causes malicious payload delivery when transfer-encoding is malformed56Plan
- CVE-2021-22883Node.js before 10.24.0, 12.21.0, 14.16.0, and 15.10.0 is vulnerable to a denial of service attack when too many connection attempts with an 53Plan
- CVE-2021-22930Node.js before 16.6.0, 14.17.4, and 12.22.4 is vulnerable to a use after free attack where an attacker might be able to exploit the memory c50Plan
Published before and after this one in the same product
- ← EarlierCVE-2022-21824Feb 24, 2022 · Due to the formatting logic of the "console.table()" function it was not safe to allow user controlled input to be passed to the "properties38Monitor
- ← EarlierCVE-2021-44533Feb 24, 2022 · Node.js < 12.22.9, < 14.18.3, < 16.13.2, and < 17.3.1 did not handle multi-value Relative Distinguished Names correctly.24Monitor
- Later →CVE-2022-32222Jul 14, 2022 · A cryptographic vulnerability exists on Node.js on linux in versions of 18.x prior to 18.40.0 which allowed a default path for openssl.cnf t22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| NodeJS Node | 10.* | Vendor (CNA) |
| NodeJS Node | 11.* | Vendor (CNA) |
| NodeJS Node | 12.* | Vendor (CNA) |
| NodeJS Node | 13.* | Vendor (CNA) |
| NodeJS Node | 14.20.1 | Vendor (CNA) |
| NodeJS Node | 15.* | Vendor (CNA) |
| NodeJS Node | 16.17.1 | Vendor (CNA) |
| NodeJS Node | 17.* | Vendor (CNA) |
| NodeJS Node | 18.9.1 | Vendor (CNA) |
| NodeJS Node | 4.* | Vendor (CNA) |
| NodeJS Node | 5.* | Vendor (CNA) |
| NodeJS Node | 6.* | Vendor (CNA) |
| NodeJS Node | 7.* | Vendor (CNA) |
| NodeJS Node | 8.* | Vendor (CNA) |
| NodeJS Node | 9.* | Vendor (CNA) |
| almalinux:nodejs | 1:14.20.0-2.module_el8.6.0+3261+490666b3 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-devel | 1:14.20.0-2.module_el8.6.0+3261+490666b3 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-docs | 1:14.20.0-2.module_el8.6.0+3261+490666b3 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-full-i18n | 1:14.20.0-2.module_el8.6.0+3261+490666b3 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-libs | 1:16.16.0-1.el9_0 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:nodejs-nodemon | 2.0.19-2.module_el8.6.0+3261+490666b3 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-packaging | 23-3.module_el8.5.0+2618+8d46dafd · AlmaLinux:8 | Package registry (OSV) |
| almalinux:npm | 1:6.14.17-1.14.20.0.2.module_el8.6.0+3261+490666b3 · AlmaLinux:8 | Package registry (OSV) |
| alpine:nodejs | 0 · Alpine:v3.13 | Package registry (OSV) |
| debian:nodejs | 18.6.0+dfsg-3 · Debian:12 | Package registry (OSV) |
| opensuse:nodejs10 | 10.24.1-150000.1.47.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| opensuse:nodejs12 | 12.22.12-150200.4.35.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| opensuse:nodejs14 | 14.20.0-150200.15.34.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| opensuse:nodejs16 | 16.16.0-150400.3.3.2 · openSUSE:Leap 15.4 | Package registry (OSV) |
| opensuse:nodejs18 | 18.13.0-150400.9.3.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
+24
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-23-0047 · Jan 25, 2023(Node JS Güvenlik Güncellemesi)
- TR-22-0615 · Sep 14, 2022(RedHat Güvenlik Güncellemesi)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-284 · Improper Access ControlCVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Embedding Scripts within ScriptsCAPEC-19likelihood: High · High
- Malicious Logic InsertionCAPEC-441likelihood: Medium · High
- Modification of Windows Service ConfigurationCAPEC-478likelihood: Low · High
- Malicious Root CertificateCAPEC-479likelihood: Low · Low
- Intent SpoofCAPEC-502
- WebView ExposureCAPEC-503
- Data Injected During ConfigurationCAPEC-536likelihood: Low · High
- Incomplete Data Deletion in a Multi-Tenant EnvironmentCAPEC-546likelihood: Low · Medium
ATT&CK techniques
- RootkitT1014
- Obfuscated Files or Information: Embedded PayloadsT1027.009
- Boot or Logon Initialization ScriptsT1037
- Taint shared contentT1080
- Server Software Component: Terminal Services DLLT1505.005
- Pre-OS Boot:BootkitT1542.003
- Create or Modify System ProcessT1543
- Create or Modify System Process: Launch AgentT1543.001
- Create or Modify System Process:Windows ServiceT1543.003
- Create or Modify System Process: Launch DaemonT1543.004
- Event Triggered Execution:Change Default File AssociationT1546.001
- Event Triggered Execution:.bash_profile and .bashrcT1546.004
- Event Triggered Execution: Accessibility FeaturesT1546.008
- Event Triggered Execution: Installer PackagesT1546.016
- Boot or Logon Autostart ExecutionT1547
- Boot or Logon Autostart Execution:Kernel Modules and ExtensionsT1547.006
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.