CVE-2021-32804: Arbitrary File Creation/Overwrite due to insufficient absolute path sanitization
Noroxi assessment
Priority: Monitor (action score 37/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 15% (FIRST EPSS); higher than 96.7% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: nodejs (AlmaLinux:8) 1:12.22.5-1.module_el8.4.0+2529+af52a4c7, 1:12.22.5-1.module_el8.5.0+85+79a7b441; nodejs-devel (AlmaLinux:8) 1:12.22.5-1.module_el8.5.0+85+79a7b441, 1:12.22.5-1.module_el8.4.0+2529+af52a4c7; nodejs-docs (AlmaLinux:8) 1:12.22.5-1.module_el8.4.0+2529+af52a4c7.
- Mentioned 3 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to nodejs (AlmaLinux:8) 1:12.22.5-1.module_el8.4.0+2529+af52a4c7, 1:12.22.5-1.module_el8.5.0+85+79a7b441; nodejs-devel (AlmaLinux:8) 1:12.22.5-1.module_el8.5.0+85+79a7b441, 1:12.22.5-1.module_el8.4.0+2529+af52a4c7; nodejs-docs (AlmaLinux:8) 1:12.22.5-1.module_el8.4.0+2529+af52a4c7 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
The npm package "tar" (aka node-tar) before versions 6.1.1, 5.0.6, 4.4.14, and 3.3.2 has a arbitrary File Creation/Overwrite vulnerability due to insufficient absolute path sanitization. node-tar aims to prevent extraction of absolute file paths by turning absolute paths into relative paths when the `preservePaths` flag is not set to `true`. This is achieved by stripping the absolute path root from any absolute file paths contained in a tar file. For example `/home/user/.bashrc` would turn into `home/user/.bashrc`. This logic was insufficient when file paths contained repeated path roots such as `////home/user/.bashrc`. `node-tar` would only strip a single path root from such paths. When given an absolute file path with repeating path roots, the resulting path (e.g. `///home/user/.bashrc`) would still resolve to an absolute path, thus allowing arbitrary file creation and overwrite. This issue was addressed in releases 3.2.2, 4.4.14, 5.0.6 and 6.1.1. Users may work around this vulnerability without upgrading by creating a custom `onentry` method which sanitizes the `entry.path` or a `filter` method which removes entries with absolute paths. See referenced GitHub Advisory for details. Be aware of CVE-2021-32803 which fixes a similar bug in later versions of tar.
- BDU:2022-00201
- GHSA-3jfq-g458-7qm9
- ALSA-2021:3623
- ALSA-2021:3666
- openSUSE-SU-2022:0657-1
- openSUSE-SU-2022:0704-1
- openSUSE-SU-2022:0715-1
- RHSA-2021:3280
- RHSA-2021:3281
- RHSA-2021:3623
- RHSA-2021:3638
- RHSA-2021:3639
- RHSA-2021:3666
- RLSA-2021:3623
- RLSA-2021:3666
- SUSE-SU-2022:0531-1
- SUSE-SU-2022:0563-1
- SUSE-SU-2022:0569-1
- SUSE-SU-2022:0570-1
- SUSE-SU-2022:0657-1
- Published
- Aug 3, 2021
- Updated
- Jun 16, 2026
- EPSS
- 15.0% · 96th percentile
- CWE
- CWE-22
Report tools
Action score
37
Monitor
Low priority for now.
- CVSS
- 32 / 40 · 8.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 5 / 30 · 15.0%
CNA vs NVD score
- NVD
- 8.1
- CNA · GitHub_M
- 8.2
- 0.1 point gap
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
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
- Proof of concept exists, no weaponized module
- 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 |
|---|---|---|
| tar project | tar | cpe:2.3:a:tar_project:tar |
| oracle | graalvm | cpe:2.3:a:oracle:graalvm |
| siemens | sinec infrastructure network services | cpe:2.3:a:siemens:sinec_infrastructure_network_services |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- oracle graalvm20.3.3
- oracle graalvm21.2.0
- siemens sinec infrastructure network servicesbefore 1.0.1.1
- tar project tarbefore 3.2.2
- tar project tar6.0.0 and later · before 6.1.1
- tar project tar4.0.0 and later · before 4.4.14
- tar project tar5.0.0 and later · before 5.0.6
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
npm node-tar
- < 3.2.2, >= 4.0.0, < 4.4.14, >= 5.0.0, < 5.0.6, >= 6.0.0, < 6.1.1affected
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:12.22.5-1.module_el8.4.0+2529+af52a4c7 | 1:12.22.5-1.module_el8.4.0+2529+af52a4c7 |
| AlmaLinux:8 | nodejs | before 1:12.22.5-1.module_el8.5.0+85+79a7b441 | 1:12.22.5-1.module_el8.5.0+85+79a7b441 |
| AlmaLinux:8 | nodejs-devel | before 1:12.22.5-1.module_el8.5.0+85+79a7b441 | 1:12.22.5-1.module_el8.5.0+85+79a7b441 |
| AlmaLinux:8 | nodejs-devel | before 1:12.22.5-1.module_el8.4.0+2529+af52a4c7 | 1:12.22.5-1.module_el8.4.0+2529+af52a4c7 |
| AlmaLinux:8 | nodejs-docs | before 1:12.22.5-1.module_el8.4.0+2529+af52a4c7 | 1:12.22.5-1.module_el8.4.0+2529+af52a4c7 |
| AlmaLinux:8 | nodejs-full-i18n | before 1:12.22.5-1.module_el8.4.0+2529+af52a4c7 | 1:12.22.5-1.module_el8.4.0+2529+af52a4c7 |
| AlmaLinux:8 | nodejs-full-i18n | before 1:12.22.5-1.module_el8.5.0+85+79a7b441 | 1:12.22.5-1.module_el8.5.0+85+79a7b441 |
| AlmaLinux:8 | nodejs-nodemon | before 2.0.3-1.module_el8.4.0+2521+c668cc9f | 2.0.3-1.module_el8.4.0+2521+c668cc9f |
| AlmaLinux:8 | nodejs-packaging | before 23-3.module_el8.5.0+254+b4526b16 | 23-3.module_el8.5.0+254+b4526b16 |
| AlmaLinux:8 | nodejs-packaging | before 17-3.module_el8.4.0+2224+b07ac28e | 17-3.module_el8.4.0+2224+b07ac28e |
| AlmaLinux:8 | nodejs-packaging | before 23-3.module_el8.4.0+2522+3bd42762 | 23-3.module_el8.4.0+2522+3bd42762 |
| AlmaLinux:8 | nodejs-packaging | before 17-3.module_el8.4.0+2521+c668cc9f | 17-3.module_el8.4.0+2521+c668cc9f |
| AlmaLinux:8 | nodejs-packaging | before 17-3.module_el8.3.0+2023+d2377ea3 | 17-3.module_el8.3.0+2023+d2377ea3 |
| AlmaLinux:8 | npm | before 1:6.14.14-1.12.22.5.1.module_el8.5.0+85+79a7b441 | 1:6.14.14-1.12.22.5.1.module_el8.5.0+85+79a7b441 |
| AlmaLinux:8 | npm | before 1:6.14.14-1.12.22.5.1.module_el8.4.0+2529+af52a4c7 | 1:6.14.14-1.12.22.5.1.module_el8.4.0+2529+af52a4c7 |
| Debian:12 | node-tar | before 6.1.7+~cs11.3.10-1 | 6.1.7+~cs11.3.10-1 |
| npm | tar | from 4.0.0 · before 4.4.14 | 4.4.14 |
| npm | tar | from 5.0.0 · before 5.0.6 | 5.0.6 |
| npm | tar | from 6.0.0 · before 6.1.1 | 6.1.1 |
| npm | tar | before 3.2.2 | 3.2.2 |
| openSUSE:Leap 15.3 | nodejs10 | before 10.24.1-150000.1.44.1 | 10.24.1-150000.1.44.1 |
| openSUSE:Leap 15.3 | nodejs12 | before 12.22.10-4.29.3 | 12.22.10-4.29.3 |
| openSUSE:Leap 15.3 | nodejs14 | before 14.19.0-15.27.1 | 14.19.0-15.27.1 |
| openSUSE:Leap 15.3 | nodejs8 | before 8.17.0-10.19.2 | 8.17.0-10.19.2 |
+63
Same product
tar project: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-32803Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning34Monitor
- CVE-2018-20990An issue was discovered in the tar crate before 0.4.16 for Rust.31Monitor
- CVE-2021-38511An issue was discovered in the tar crate before 0.4.36 for Rust.30Monitor
Published before and after this one in the same product
- Later →CVE-2026-33056Mar 20, 2026 · tar-rs: unpack_in can chmod arbitrary directories by following symlinks20Monitor
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 |
|---|---|---|
| almalinux:nodejs | 1:12.22.5-1.module_el8.4.0+2529+af52a4c7 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-devel | 1:12.22.5-1.module_el8.5.0+85+79a7b441 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-docs | 1:12.22.5-1.module_el8.4.0+2529+af52a4c7 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-full-i18n | 1:12.22.5-1.module_el8.5.0+85+79a7b441 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-nodemon | 2.0.3-1.module_el8.4.0+2521+c668cc9f · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-packaging | 17-3.module_el8.4.0+2224+b07ac28e · AlmaLinux:8 | Package registry (OSV) |
| almalinux:npm | 1:6.14.14-1.12.22.5.1.module_el8.4.0+2529+af52a4c7 · AlmaLinux:8 | Package registry (OSV) |
| alpine:tar | 0 · Alpine:v3.16 | Package registry (OSV) |
| debian:node-tar | 6.1.7+~cs11.3.10-1 · Debian:12 | Package registry (OSV) |
| npm:tar | 3.2.2 | Package registry (OSV) |
| npm:tar | 4.4.14 | Package registry (OSV) |
| npm:tar | 5.0.6 | Package registry (OSV) |
| npm:tar | 6.1.1 | Package registry (OSV) |
| opensuse:nodejs10 | 10.24.1-150000.1.44.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| opensuse:nodejs12 | 12.22.10-4.29.3 · openSUSE:Leap 15.3 | Package registry (OSV) |
| opensuse:nodejs14 | 14.19.0-15.27.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| opensuse:nodejs8 | 8.17.0-10.19.2 · openSUSE:Leap 15.3 | Package registry (OSV) |
| red hat:rh-nodejs12-nodejs | 0:12.22.5-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-nodejs12-nodejs-debuginfo | 0:12.22.5-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-nodejs12-nodejs-devel | 0:12.22.5-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-nodejs12-nodejs-docs | 0:12.22.5-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-nodejs12-nodejs-nodemon | 0:2.0.3-5.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-nodejs12-npm | 0:6.14.14-12.22.5.1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-nodejs14-nodejs | 0:14.17.5-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-nodejs14-nodejs-debuginfo | 0:14.17.5-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-nodejs14-nodejs-devel | 0:14.17.5-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-nodejs14-nodejs-docs | 0:14.17.5-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-nodejs14-nodejs-nodemon | 0:2.0.3-5.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-nodejs14-npm | 0:6.14.14-14.17.5.1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| rocky linux:nodejs | 1:12.22.5-1.module+el8.4.0+647+e905fa21 · Rocky Linux:8 | Package registry (OSV) |
+8
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:1 | 2021-08-31 |
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.
- Published
- First PoC+27 d
- TodayNov 4, 2026+1919 d
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.
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
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-22-0215 · Mar 11, 2022(Siemens Güvenlik Bildirimi)
- TR-21-0921 · Nov 16, 2021(IBM Güvenlik Bülteni Yayınladı)
- TR-21-0779 · Sep 28, 2021(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.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H
nvd-primary
Root cause
A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.
The bug in code
The whole CWE-22 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const file = path.join(ROOT, req.query.name);
res.sendFile(file);Fixed
const file = path.resolve(ROOT, req.query.name);
if (!file.startsWith(ROOT + path.sep)) {
return res.sendStatus(400);
}
res.sendFile(file);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)
- Path TraversalCAPEC-126likelihood: High · Very High
- Using Slashes and URL Encoding Combined to Bypass Validation LogicCAPEC-64likelihood: High · High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
- Using Escaped Slashes in Alternate EncodingCAPEC-78likelihood: High · High
- Using Slashes in Alternate EncodingCAPEC-79likelihood: High · High
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.