forked from jwillebrands/whitesource-demo
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CVE-2021-37701 (High) detected in tar-4.4.13.tgz #55
Labels
Mend: dependency security vulnerability
Security vulnerability detected by WhiteSource
Comments
mend-for-github-com
bot
added
the
Mend: dependency security vulnerability
Security vulnerability detected by WhiteSource
label
Feb 7, 2022
This was referenced Feb 7, 2022
mend-for-github-com
bot
changed the title
CVE-2021-37701 (High) detected in multiple libraries
CVE-2021-37701 (High) detected in tar-4.4.8.tgz, tar-4.4.11.tgz
Feb 20, 2022
mend-for-github-com
bot
changed the title
CVE-2021-37701 (High) detected in tar-4.4.8.tgz, tar-4.4.11.tgz
CVE-2021-37701 (High) detected in multiple libraries
Feb 20, 2022
mend-for-github-com
bot
changed the title
CVE-2021-37701 (High) detected in multiple libraries
CVE-2021-37701 (High) detected in tar-4.4.11.tgz, tar-4.4.8.tgz
Feb 22, 2022
mend-for-github-com
bot
changed the title
CVE-2021-37701 (High) detected in tar-4.4.11.tgz, tar-4.4.8.tgz
CVE-2021-37701 (High) detected in tar-4.4.8.tgz, tar-4.4.11.tgz
Mar 22, 2022
mend-for-github-com
bot
changed the title
CVE-2021-37701 (High) detected in tar-4.4.8.tgz, tar-4.4.11.tgz
CVE-2021-37701 (High) detected in tar-4.4.8.tgz, tar-4.4.11.tgz - autoclosed
Jun 19, 2022
✔️ This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory. |
mend-for-github-com
bot
changed the title
CVE-2021-37701 (High) detected in tar-4.4.8.tgz, tar-4.4.11.tgz - autoclosed
CVE-2021-37701 (High) detected in tar-4.4.13.tgz
Jan 7, 2023
ℹ️ This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory. |
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Mend: dependency security vulnerability
Security vulnerability detected by WhiteSource
0 participants
CVE-2021-37701 - High Severity Vulnerability
Vulnerable Library - tar-4.4.13.tgz
tar for node
Library home page: https://registry.npmjs.org/tar/-/tar-4.4.13.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/tar/package.json
Dependency Hierarchy:
Found in HEAD commit: 2a1411ba78280c07796558559ccfca7738c05cf4
Found in base branch: master
Vulnerability Details
The npm package "tar" (aka node-tar) before versions 4.4.16, 5.0.8, and 6.1.7 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. node-tar aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary stat calls to determine whether a given path is a directory, paths are cached when directories are created. This logic was insufficient when extracting tar files that contained both a directory and a symlink with the same name as the directory, where the symlink and directory names in the archive entry used backslashes as a path separator on posix systems. The cache checking logic used both
\
and/
characters as path separators, however\
is a valid filename character on posix systems. By first creating a directory, and then replacing that directory with a symlink, it was thus possible to bypass node-tar symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite. Additionally, a similar confusion could arise on case-insensitive filesystems. If a tar archive contained a directory atFOO
, followed by a symbolic link namedfoo
, then on case-insensitive file systems, the creation of the symbolic link would remove the directory from the filesystem, but not from the internal directory cache, as it would not be treated as a cache hit. A subsequent file entry within theFOO
directory would then be placed in the target of the symbolic link, thinking that the directory had already been created. These issues were addressed in releases 4.4.16, 5.0.8 and 6.1.7. 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. If this is not possible, a workaround is available in the referenced GHSA-9r2w-394v-53qc.Publish Date: 2021-08-31
URL: CVE-2021-37701
CVSS 3 Score Details (8.6)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-9r2w-394v-53qc
Release Date: 2021-08-31
Fix Resolution (tar): 4.4.16
Direct dependency fix Resolution (firebase-tools): 7.1.1
⛑️ Automatic Remediation will be attempted for this issue.
The text was updated successfully, but these errors were encountered: