CVE-2021-37713

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.

Severity
HIGH
CVSS v3
8.2
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N · source cna
Exploit chance (EPSS)
1.273%
chance of exploitation in the next 30 days
higher than 70.4% of scored CVEs · 2026-11-17
CISA KEV
Not listed
Public exploit code
None public
Exploit references (NVD and CNA): 0
Metasploit modules: 0
Nuclei templates: 0

Weakness

Timeline

  1. 2021-08-31Published by the CNA16:50 UTC
  2. 2021-08-31GitHub advisory published (GHSA-5955-9wpr-37jh)same day

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Exploit and advisory records

GitHub advisory GHSA-5955-9wpr-37jh, affected packages:

PackageVulnerable versionsFixed in
npm tarbefore 4.4.184.4.18
npm tarfrom 5.0.0 before 5.0.105.0.10
npm tarfrom 6.0.0 before 6.1.96.1.9

Affected products

Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.

ProductVulnerable versionsFixed in
npmjs tarbefore 4.4.18fixed in 4.4.18from 5.0.0 before 5.0.10fixed in 5.0.10from 6.0.0 before 6.1.9fixed in 6.1.94.4.185.0.106.1.9
oracle graalvm20.3.3no fix listed21.2.0no fix listednot listednot listed
siemens sinec_infrastructure_network_servicesbefore 1.0.1.1fixed in 1.0.1.11.0.1.1

Products and versions as NVD and the vendor that published the CVE list them.

References

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources