CVE-2021-37713: Arbitrary File Creation/Overwrite on Windows via insufficient relative path sanitization
Vulnerability summary
CVE-2021-37713 is a high (CVSS 8.6) vulnerability in npmjs tar. EPSS estimates a 1.27% chance of exploitation in the next 30 days, higher than 69.9% of scored vulnerabilities.
Not severe (CVSS 8.2, local access); no exploitation reported by the 5 checked sources
Source freshness unavailable
How is this decided?Advisory lineage
Upstream 0 · Downstream 10 · Related 10Timeline
- 31-08-2021PublishedVulnerability first disclosed.
- 04-08-2024Last modifiedVulnerability information updated.
Description
The npm package "tar" (aka node-tar) before versions 4.4.18, 5.0.10, and 6.1.9 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. node-tar aims to guarantee that any file whose location would be outside of the extraction target directory is not extracted. This is, in part, accomplished by sanitizing absolute paths of entries within the archive, skipping archive entries that contain `..` path portions, and resolving the sanitized paths against the extraction target directory. This logic was insufficient on Windows systems when extracting tar files that contained a path that was not an absolute path, but specified a drive letter different from the extraction target, such as `C:some\path`. If the drive letter does not match the extraction target, for example `D:\extraction\dir`, then the result of `path.resolve(extractionDirectory, entryPath)` would resolve against the current working directory on the `C:` drive, rather than the extraction target directory. Additionally, a `..` portion of the path could occur immediately after the drive letter, such as `C:../foo`, and was not properly sanitized by the logic that checked for `..` within the normalized and split portions of the path. This only affects users of `node-tar` on Windows systems. These issues were addressed in releases 4.4.18, 5.0.10 and 6.1.9. The v3 branch of node-tar has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of node-tar. There is no reasonable way to work around this issue without performing the same path normalization procedures that node-tar now does. Users are encouraged to upgrade to the latest patched versions of node-tar, rather than attempt to sanitize paths themselves.
CVSS metrics
5 scores · 4 sources · 2 versions- CVE.orgCNA8.2HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:NDiffers
- OSV · AlpineEcosystem advisory · calculated8.6HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
- OSV · NpmEcosystem advisory · calculated8.2HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:NDiffers
EPSS trend
Probability
1.27%
Chance of exploitation in the next 30 days
Percentile
70%
Versus all other CVEs
30-day change
Increase +0.01 pp
From 1.26% on 04-10-2026
Known exploited
Compare KEV catalogsNot in the CISA KEV catalog.
Not in the ENISA CNW catalog.
Not in the CIRCL catalog.
Public exploits
0 foundNo public exploits indexed.
Weaknesses
CWE · root causeAffected systems
Known conditions: local access, no authentication, user interaction (CVSS vector). Other conditions: not stated in public data.
Npm2 products
- node-tar< 4.4.18 | ≥ 5.0.0, < 5.0.10 | ≥ 6.0.0, < 6.1.9
- tar< 4.4.18 | ≥ 5.0.0, < 5.0.10 | ≥ 6.0.0, < 6.1.9
Alpine1 product
- nodejs< 12.22.6-r0 | < 14.17.6-r0
Npmjs1 product
- tar< 4.4.18 | ≥ 5.0.0, < 5.0.10 | ≥ 6.0.0, < 6.1.9
Oracle1 product
- graalvmEOL20.3.3 | 21.2.0
Siemens1 product
5 vendors · 6 products
References
10 links- github.com/npm/node-tar/security/advisories/GHSA-5955-9wpr-37jhX Refsource CONFIRMWEBPatchThird Party Advisory
- cert-portal.siemens.com/productcert/pdf/ssa-389290.pdfX Refsource CONFIRMWEBPatchThird Party Advisory
- github.com/npm/node-tarPACKAGE