8.6

CVE-2021-37712: Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning using symbolic links

Modified
AliasesALPINE-CVE-2021-37712UBUNTU-CVE-2021-37712DEBIAN-CVE-2021-37712
Published 31-08-2021Last modified 04-08-2024

Vulnerability summary

CVE-2021-37712 is a high (CVSS 8.6) vulnerability in debian debian_linux. EPSS estimates a 1.86% chance of exploitation in the next 30 days, higher than 79.3% 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.86%
0%100%
Low · +0.02 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 20 · Related 8

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 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 names containing unicode values that normalized to the same value. Additionally, on Windows systems, long path portions would resolve to the same file system entities as their 8.3 "short path" counterparts. A specially crafted tar archive could thus include a directory with one form of the path, followed by a symbolic link with a different string that resolves to the same file system entity, followed by a file using the first form. By first creating a directory, and then replacing that directory with a symlink that had a different apparent name that resolved to the same entry in the filesystem, 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. 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. If this is not possible, a workaround is available in the referenced GHSA-qq89-hq3f-393p.

CVSS metrics

7 scores · 6 sources · 2 versions

EPSS trend

Probability

1.86%

Chance of exploitation in the next 30 days

Percentile

79%

Versus all other CVEs

30-day change

Increase +0.02 pp

From 1.85% 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.

Debian2 products
Npm2 products
  • node-tar< 4.4.18 | ≥ 5.0.0, < 5.0.10 | ≥ 6.0.0, < 6.1.9
  • tar≥ 3.0.0, < 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.17 | ≥ 5.0.0, ≤ 5.0.9 | ≥ 6.0.0, ≤ 6.1.8
Oracle1 product
Siemens1 product
Ubuntu1 product
  • node-tarAll versions (No fix recorded)

7 vendors · 9 products

References

18 links
Show all 18 references