8.6

CVE-2021-37713: Arbitrary File Creation/Overwrite on Windows via insufficient relative path sanitization

Modified
AliasesALPINE-CVE-2021-37713GHSA-5955-9wpr-37jh
Published 31-08-2021Last modified 04-08-2024

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.

Priority
Routine

Not severe (CVSS 8.2, local access); no exploitation reported by the 5 checked sources

Source freshness unavailable

How is this decided?
CVSS score
8.6/10
010
High · v3.1 (NVD)
EPSS score
1.27%
0%100%
Low · +0.01 pp in 30 days
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 10 · Related 10

Timeline

  1. 31-08-2021
    PublishedVulnerability first disclosed.
  2. 04-08-2024
    Last 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

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

04-10-202603-11-2026

Known exploited

Compare KEV catalogs
CISA KEV

Not in the CISA KEV catalog.

ENISA CNW

Not in the ENISA CNW catalog.

CIRCL

Not in the CIRCL catalog.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Version check

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
Siemens1 product

5 vendors · 6 products

References

10 links