You are viewing this page in an unauthorized frame window.
This is a potential security issue, you are being redirected to https://nvd.nist.gov
An official website of the United States government
Official websites use .gov
A .gov website belongs to an official government organization in the United States.
Secure .gov websites use HTTPS
A lock () or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.
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.
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.
NVD Analysts use publicly available information to associate vector strings and CVSS scores. We also display any CVSS information provided within the CVE List from the CNA.
Note: It is possible that the NVD CVSS may not match that of the CNA. The most common reason for this is that publicly available information does not provide sufficient detail or that information simply was not available at the time the CVSS vector string was assigned.
NVD Analysts use publicly available information to associate vector strings and CVSS scores. We also display any CVSS information provided within the CVE List from the CNA.
Note: NVD Analysts have published a CVSS score for this CVE based on publicly available information at the time of analysis. The CNA has not provided a score within the CVE List.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to nvd@nist.gov.
OR
*cpe:2.3:a:siemens:sinec_infrastructure_network_services:*:*:*:*:*:*:*:* versions up to (excluding) 1.0.1.1
Changed
CPE Configuration
AND
OR
*cpe:2.3:a:npmjs:tar:*:*:*:*:*:node.js:*:* versions up to (including) 4.4.17
*cpe:2.3:a:npmjs:tar:*:*:*:*:*:node.js:*:* versions from (including) 5.0.0 up to (including) 5.0.9
*cpe:2.3:a:npmjs:tar:*:*:*:*:*:node.js:*:* versions from (including) 6.0.0 up to (including) 6.1.8
OR
cpe:2.3:o:microsoft:windows:-:*:*:*:*:*:*:*
AND
OR
*cpe:2.3:a:npmjs:tar:*:*:*:*:*:node.js:*:* versions up to (excluding) 4.4.18
*cpe:2.3:a:npmjs:tar:*:*:*:*:*:node.js:*:* versions from (including) 5.0.0 up to (excluding) 5.0.10
*cpe:2.3:a:npmjs:tar:*:*:*:*:*:node.js:*:* versions from (including) 6.0.0 up to (excluding) 6.1.9
OR
cpe:2.3:o:microsoft:windows:-:*:*:*:*:*:*:*
Changed
Reference Type
https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf No Types Assigned
https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf Patch, Third Party Advisory
AND
OR
*cpe:2.3:a:npmjs:tar:*:*:*:*:*:node.js:*:* versions up to (including) 4.4.17
*cpe:2.3:a:npmjs:tar:*:*:*:*:*:node.js:*:* versions from (including) 5.0.0 up to (including) 5.0.9
*cpe:2.3:a:npmjs:tar:*:*:*:*:*:node.js:*:* versions from (including) 6.0.0 up to (including) 6.1.8
OR
cpe:2.3:o:microsoft:windows:-:*:*:*:*:*:*:*
Added
CVSS V2
NIST (AV:L/AC:M/Au:N/C:P/I:P/A:P)
Added
CVSS V2 Metadata
Victim must voluntarily interact with attack mechanism
Added
CVSS V3.1
NIST AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Changed
Reference Type
https://github.com/npm/node-tar/security/advisories/GHSA-5955-9wpr-37jh No Types Assigned
https://github.com/npm/node-tar/security/advisories/GHSA-5955-9wpr-37jh Patch, Third Party Advisory
Changed
Reference Type
https://www.npmjs.com/package/tar No Types Assigned
https://www.npmjs.com/package/tar Product, Third Party Advisory
Quick Info
CVE Dictionary Entry: CVE-2021-37713 NVD
Published Date: 08/31/2021 NVD
Last Modified: 04/25/2022
Source: GitHub, Inc.
) or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.
