CVE-2021-37701

Description

The npm package "tar" (aka node-tar) before versions 4.4.16, 5.0.8, and 6.1.7 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. node-tar aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary stat calls to determine whether a given path is a directory, paths are cached when directories are created. This logic was insufficient when extracting tar files that contained both a directory and a symlink with the same name as the directory, where the symlink and directory names in the archive entry used backslashes as a path separator on posix systems. The cache checking logic used both `\` and `/` characters as path separators, however `\` is a valid filename character on posix systems. By first creating a directory, and then replacing that directory with a symlink, it was thus possible to bypass node-tar symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite. Additionally, a similar confusion could arise on case-insensitive filesystems. If a tar archive contained a directory at `FOO`, followed by a symbolic link named `foo`, then on case-insensitive file systems, the creation of the symbolic link would remove the directory from the filesystem, but _not_ from the internal directory cache, as it would not be treated as a cache hit. A subsequent file entry within the `FOO` directory would then be placed in the target of the symbolic link, thinking that the directory had already been created. These issues were addressed in releases 4.4.16, 5.0.8 and 6.1.7. 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. If this is not possible, a workaround is available in the referenced GHSA-9r2w-394v-53qc.

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)
3.286%
chance of exploitation in the next 30 days
higher than 88.7% 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 CNA00:00 UTC
  2. 2021-08-31GitHub advisory published (GHSA-9r2w-394v-53qc)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-9r2w-394v-53qc, affected packages:

PackageVulnerable versionsFixed in
npm tarfrom 3.0.0 before 4.4.164.4.16
npm tarfrom 5.0.0 before 5.0.85.0.8
npm tarfrom 6.0.0 before 6.1.76.1.7

Affected products

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

ProductVulnerable versionsFixed in
npmjs tarbefore 4.4.16fixed in 4.4.16from 5.0.0 before 5.0.8fixed in 5.0.8from 6.0.0 before 6.1.7fixed in 6.1.74.4.165.0.86.1.7
debian debian_linux10.0no fix listed11.0no fix listednot listednot listed
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