We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.

Please see our statement on Data Privacy.

Crisp.chat (Helpdesk and Chat)

Ok

THREATINT
PUBLISHED

CVE-2021-37713

Arbitrary File Creation/Overwrite on Windows via insufficient relative path sanitization



AssignerGitHub_M
Reserved2021-07-29
Published2021-08-31
Updated2024-08-04

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.



HIGH: 8.2CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N

Product status

< 4.4.18
affected

>= 5.0.0, < 5.0.10
affected

>= 6.0.0, < 6.1.9
affected

References

https://www.npmjs.com/package/tar

https://github.com/npm/node-tar/security/advisories/GHSA-5955-9wpr-37jh

https://www.oracle.com/security-alerts/cpuoct2021.html

https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf

cve.org CVE-2021-37713

nvd.nist.gov CVE-2021-37713

Download JSON

Share this page
https://cve.threatint.com/CVE/CVE-2021-37713
Support options

Helpdesk Telegram

Subscribe to our newsletter to learn more about our work.