CVE-2024-22020: A security flaw in Node.js allows a bypass of network import restrictions.
Noroxi assessment
Priority: Monitor (action score 26/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: 1.1% (FIRST EPSS); higher than 65.5% of all records.
- Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. Special conditions such as timing or configuration are required.
- Fixed version: NodeJS Node 10.*, 11.*, 12.*; azl3 nodejs 20.14.0-5 on Azure Linux 3.0 20.14.0-5; azl3 nodejs 20.14.0-8 on Azure Linux 3.0 20.14.0-5.
Low priority for now. Upgrade to NodeJS Node 10.*, 11.*, 12.*; azl3 nodejs 20.14.0-5 on Azure Linux 3.0 20.14.0-5; azl3 nodejs 20.14.0-8 on Azure Linux 3.0 20.14.0-5 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 security flaw in Node.js allows a bypass of network import restrictions. By embedding non-network imports in data URLs, an attacker can execute arbitrary code, compromising system security. Verified on various platforms, the vulnerability is mitigated by forbidding data URLs in network imports. Exploiting this flaw can violate network import security, posing a risk to developers and servers.
- BDU:2024-06867
- ALSA-2024:5814
- ALSA-2024:5815
- ALSA-2024:6147
- ALSA-2024:6148
- DSA-5991-1
- openSUSE-SU-2024:14214-1
- openSUSE-SU-2024:14435-1
- openSUSE-SU-2025:15802-1
- openSUSE-SU-2026:11110-1
- RHSA-2024:5814
- RHSA-2024:5815
- RHSA-2024:6147
- RHSA-2024:6148
- RLSA-2024:5814
- RLSA-2024:5815
- RLSA-2024:6147
- RLSA-2024:6148
- SUSE-SU-2024:2496-1
- SUSE-SU-2024:2542-1
- Published
- Jul 8, 2024
- Updated
- Jun 17, 2026
- EPSS
- 1.1% · 65th percentile
- CWE
- CWE-94
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · hackerone
- 6.5
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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 | nodejs | cpe:2.3:a:nodejs:nodejs |
Using node? Add it to your stack and be the first to know about CVEs like this one. (Node.js)
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:20.16.0-1.module_el8.10.0+3882+e12e42db | 1:20.16.0-1.module_el8.10.0+3882+e12e42db |
| AlmaLinux:8 | nodejs | before 1:18.20.4-1.module_el8.10.0+3890+5a092792 | 1:18.20.4-1.module_el8.10.0+3890+5a092792 |
| AlmaLinux:8 | nodejs-devel | before 1:18.20.4-1.module_el8.10.0+3890+5a092792 | 1:18.20.4-1.module_el8.10.0+3890+5a092792 |
| AlmaLinux:8 | nodejs-devel | before 1:20.16.0-1.module_el8.10.0+3882+e12e42db | 1:20.16.0-1.module_el8.10.0+3882+e12e42db |
| AlmaLinux:8 | nodejs-docs | before 1:18.20.4-1.module_el8.10.0+3890+5a092792 | 1:18.20.4-1.module_el8.10.0+3890+5a092792 |
| AlmaLinux:8 | nodejs-docs | before 1:20.16.0-1.module_el8.10.0+3882+e12e42db | 1:20.16.0-1.module_el8.10.0+3882+e12e42db |
| AlmaLinux:8 | nodejs-full-i18n | before 1:18.20.4-1.module_el8.10.0+3890+5a092792 | 1:18.20.4-1.module_el8.10.0+3890+5a092792 |
| AlmaLinux:8 | nodejs-full-i18n | before 1:20.16.0-1.module_el8.10.0+3882+e12e42db | 1:20.16.0-1.module_el8.10.0+3882+e12e42db |
| AlmaLinux:8 | nodejs-nodemon | before 3.0.1-1.module_el8.9.0+3731+490e3ce5 | 3.0.1-1.module_el8.9.0+3731+490e3ce5 |
| AlmaLinux:8 | nodejs-nodemon | before 3.0.1-1.module_el8.8.0+3613+1ed8c91d | 3.0.1-1.module_el8.8.0+3613+1ed8c91d |
| AlmaLinux:8 | nodejs-packaging | before 2021.06-4.module_el8.7.0+3343+ea2b7901 | 2021.06-4.module_el8.7.0+3343+ea2b7901 |
| AlmaLinux:8 | nodejs-packaging | before 2021.06-4.module_el8.9.0+3775+d8460d35 | 2021.06-4.module_el8.9.0+3775+d8460d35 |
| AlmaLinux:8 | nodejs-packaging-bundler | before 2021.06-4.module_el8.9.0+3775+d8460d35 | 2021.06-4.module_el8.9.0+3775+d8460d35 |
| AlmaLinux:8 | nodejs-packaging-bundler | before 2021.06-4.module_el8.7.0+3343+ea2b7901 | 2021.06-4.module_el8.7.0+3343+ea2b7901 |
| AlmaLinux:8 | npm | before 1:10.8.1-1.20.16.0.1.module_el8.10.0+3882+e12e42db | 1:10.8.1-1.20.16.0.1.module_el8.10.0+3882+e12e42db |
| AlmaLinux:8 | npm | before 1:10.7.0-1.18.20.4.1.module_el8.10.0+3890+5a092792 | 1:10.7.0-1.18.20.4.1.module_el8.10.0+3890+5a092792 |
| AlmaLinux:9 | nodejs | before 1:18.20.4-1.module_el9.4.0+112+bb28ff81 | 1:18.20.4-1.module_el9.4.0+112+bb28ff81 |
| AlmaLinux:9 | nodejs | before 1:20.16.0-1.module_el9.4.0+107+dbd477e4 | 1:20.16.0-1.module_el9.4.0+107+dbd477e4 |
| AlmaLinux:9 | nodejs-devel | before 1:18.20.4-1.module_el9.4.0+112+bb28ff81 | 1:18.20.4-1.module_el9.4.0+112+bb28ff81 |
| AlmaLinux:9 | nodejs-devel | before 1:20.16.0-1.module_el9.4.0+107+dbd477e4 | 1:20.16.0-1.module_el9.4.0+107+dbd477e4 |
| AlmaLinux:9 | nodejs-docs | before 1:18.20.4-1.module_el9.4.0+112+bb28ff81 | 1:18.20.4-1.module_el9.4.0+112+bb28ff81 |
| AlmaLinux:9 | nodejs-docs | before 1:20.16.0-1.module_el9.4.0+107+dbd477e4 | 1:20.16.0-1.module_el9.4.0+107+dbd477e4 |
| AlmaLinux:9 | nodejs-full-i18n | before 1:18.20.4-1.module_el9.4.0+112+bb28ff81 | 1:18.20.4-1.module_el9.4.0+112+bb28ff81 |
| AlmaLinux:9 | nodejs-full-i18n | before 1:20.16.0-1.module_el9.4.0+107+dbd477e4 | 1:20.16.0-1.module_el9.4.0+107+dbd477e4 |
+79
Same product
nodejs: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-27983An attacker can make the Node.js HTTP/2 server completely unavailable by sending a small amount of HTTP/2 frames packets with a few HTTP/2 f58Plan
- CVE-2025-27210An incomplete fix has been identified for CVE-2025-23084 in Node.js, specifically affecting Windows device names like CON, PRN, and AUX.34Monitor
- CVE-2024-27980Due to the improper handling of batch files in child_process.spawn / child_process.spawnSync, a malicious command line argument can inject a32Monitor
Published before and after this one in the same product
- ← EarlierCVE-2024-22025Mar 19, 2024 · A vulnerability in Node.js has been identified, allowing for a Denial of Service (DoS) attack through resource exhaustion when using the fet26Monitor
- ← EarlierCVE-2024-27982May 7, 2024 · The team has identified a critical vulnerability in the http server of the most recent version of Node, where malformed headers can lead to 26Monitor
- Later →CVE-2024-22018Jul 9, 2024 · A vulnerability has been identified in Node.js, affecting users of the experimental permission model when the --allow-fs-read flag is used.11Monitor
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.* | Vendor (CNA) |
| NodeJS Node | 15.* | Vendor (CNA) |
| NodeJS Node | 16.* | Vendor (CNA) |
| NodeJS Node | 17.* | Vendor (CNA) |
| NodeJS Node | 18.20.4 | Vendor (CNA) |
| NodeJS Node | 19.* | Vendor (CNA) |
| NodeJS Node | 20.15.1 | Vendor (CNA) |
| NodeJS Node | 21.* | Vendor (CNA) |
| NodeJS Node | 22.4.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) |
| azl3 nodejs 20.14.0-5 on Azure Linux 3.0 | 20.14.0-5 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 nodejs 20.14.0-8 on Azure Linux 3.0 | 20.14.0-5 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 nodejs18 18.20.3-3 on CBL Mariner 2.0 | 18.20.3-3 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 nodejs18 18.20.3-5 on CBL Mariner 2.0 | 18.20.3-3 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:nodejs | 1:20.16.0-1.module_el8.10.0+3882+e12e42db · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-devel | 1:20.16.0-1.module_el8.10.0+3882+e12e42db · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-docs | 1:20.16.0-1.module_el8.10.0+3882+e12e42db · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-full-i18n | 1:20.16.0-1.module_el8.10.0+3882+e12e42db · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-nodemon | 3.0.1-1.module_el8.9.0+3731+490e3ce5 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-packaging | 2021.06-4.module_el8.9.0+3775+d8460d35 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-packaging-bundler | 2021.06-4.module_el8.9.0+3775+d8460d35 · AlmaLinux:8 | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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.
- CVE-2023-3933361 days apartMaliciously crafted export names in an imported WebAssembly module can inject JavaScript code.21Monitor
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.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- low · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-94 · Improper Control of Generation of Code ('Code Injection')CVSS vector
CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:H/A:H
nvd-secondary
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)
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.