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.
Weakness
- CWE-22: Improper Limitation of a Pathname to a Restricted Directory
Timeline
- 2021-08-31Published by the CNA16:50 UTC
- 2021-08-31GitHub advisory published (GHSA-5955-9wpr-37jh)same day
Exploit and advisory records
GitHub advisory GHSA-5955-9wpr-37jh, affected packages:
| Package | Vulnerable versions | Fixed in |
|---|---|---|
| npm tar | before 4.4.18 | 4.4.18 |
| npm tar | from 5.0.0 before 5.0.10 | 5.0.10 |
| npm tar | from 6.0.0 before 6.1.9 | 6.1.9 |
Affected products
Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.
| Product | Vulnerable versions | Fixed in |
|---|---|---|
| npmjs tar | before 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.9 | 4.4.185.0.106.1.9 |
| oracle graalvm | 20.3.3no fix listed21.2.0no fix listed | not listednot listed |
| siemens sinec_infrastructure_network_services | before 1.0.1.1fixed in 1.0.1.1 | 1.0.1.1 |
References
- https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf
- https://github.com/npm/node-tar/security/advisories/GHSA-5955-9wpr-37jh
- https://www.oracle.com/security-alerts/cpuoct2021.html
- https://www.npmjs.com/package/tar
Get more CVE data from the API.
curl 'https://api.contrastcyber.com/cve_lookup/CVE-2021-37713'curl 'https://api.contrastcyber.com/cve_risk_score/CVE-2021-37713'curl 'https://api.contrastcyber.com/cve_exploit/CVE-2021-37713'curl 'https://api.contrastcyber.com/cve_products/CVE-2021-37713'
Sources
- Vulnerability data from the National Vulnerability Database (NIST) and the CVE Program. CVE records: Copyright © 1999-2026, The MITRE Corporation, used under the CVE Program Terms of Use. CVE® is a registered trademark of The MITRE Corporation.
- CWE definitions: Copyright © 2006-2026, The MITRE Corporation, used under the CWE Terms of Use. CWE is a trademark of The MITRE Corporation.
- OWASP Top 10 categories by the OWASP Foundation (CC BY 3.0).
- EPSS scores by FIRST.org EPSS, used with attribution.
- KEV catalog and SSVC decisions by CISA.
- Advisory data from the GitHub Advisory Database through OSV.dev (CC BY 4.0).
- Exploit metadata from the Exploit Database (GPL-2.0-only, metadata only).
- Nuclei template names from nuclei-templates (MIT).