CVE-2021-37713

Aliases:GHSA-5955-9wpr-37jh
Advisory lineage Upstream: 0 Downstream: 11
Modified
Published: 31 Aug 2021, 16:50
Last modified:04 Aug 2024, 01:23

Vulnerability Summary

Overall Risk (default)
medium
34/100
CVSS Score
8.6 HIGH
v3.1 (nvd)
EPSS Score
0.32% LOW
0% probability -0.29%
KEV
Not listed
Ransomware
No reports
Public exploits
None found
Dark Web
Not detected

Timeline

31 Aug 2021, 16:50
Published
Vulnerability first disclosed
04 Aug 2024, 01:23
Last Modified
Vulnerability 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

  • v3.1•HIGH•Score: 8.2CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
  • v3.1•HIGH•Score: 8.6CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
  • v2.0•MEDIUM•Score: 4.4AV:L/AC:M/Au:N/C:P/I:P/A:P

EPSS Trends

Current EPSS score: 0.32%• Percentile: 55%

Techniques & Countermeasures

  • CWE-22•Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

    The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

Affected Systems

  • npm•node-tar

    < 4.4.18 | ≥ 5.0.0, < 5.0.10 | ≥ 6.0.0, < 6.1.9

  • Npm•tar

    < 4.4.18 | ≥ 5.0.0, < 5.0.10 | ≥ 6.0.0, < 6.1.9

  • npmjs•tar

    < 4.4.18 | ≥ 5.0.0, < 5.0.10 | ≥ 6.0.0, < 6.1.9

  • oracle•graalvm

    20.3.3 | 21.2.0

  • siemens•sinec_infrastructure_network_services

    < 1.0.1.1

References (9)