You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
tar is a full-featured Tar for Node.js.
Affected versions of this package are vulnerable to Arbitrary File Write. 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 is insufficient on Windows systems when extracting tar files that contain a path that is not an absolute path, but specify 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) resolves against the current working directory on the C: drive, rather than the extraction target directory.
Additionally, a .. portion of the path can occur immediately after the drive letter, such as C:../foo, and is not properly sanitized by the logic that checks for .. within the normalized and split portions of the path.
Note: This only affects users of node-tar on Windows systems.
Remediation
Upgrade tar to version 6.1.9, 5.0.10, 4.4.18 or higher.
Detailed paths
Overview
tar is a full-featured Tar for Node.js.
Affected versions of this package are vulnerable to Arbitrary File Write.
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 is insufficient on Windows systems when extracting
tar
files that contain a path that is not an absolute path, but specify a drive letter different from the extraction target, such asC:some\path
. If the drive letter does not match the extraction target, for exampleD:\extraction\dir
, then the result ofpath.resolve(extractionDirectory, entryPath)
resolves against the current working directory on theC:
drive, rather than the extraction target directory.Additionally, a
..
portion of the path can occur immediately after the drive letter, such asC:../foo
, and is not properly sanitized by the logic that checks for..
within the normalized and split portions of the path.Note: This only affects users of
node-tar
on Windows systems.Remediation
Upgrade
tar
to version 6.1.9, 5.0.10, 4.4.18 or higher.References
SNYK-JS-TAR-1579155
(CVE-2021-37713) tar@2.2.2
The text was updated successfully, but these errors were encountered: