Vulnerable Library - strider-ssh-deploy-1.0.0.tgz
Path to dependency file: /apps/strider/package.json
Path to vulnerable library: /apps/strider/node_modules/tar/node_modules/fstream/package.json
Found in HEAD commit: ee765c82cdb8fda389b5b028a35744c8dc2be1a9
Vulnerabilities
Details
CVE-2020-26301
Vulnerable Library - ssh2-0.4.15.tgz
SSH2 client and server modules written in pure JavaScript for node.js
Library home page: https://registry.npmjs.org/ssh2/-/ssh2-0.4.15.tgz
Path to dependency file: /apps/strider/package.json
Path to vulnerable library: /apps/strider/node_modules/ssh2/package.json
Dependency Hierarchy:
- strider-ssh-deploy-1.0.0.tgz (Root Library)
- ❌ ssh2-0.4.15.tgz (Vulnerable Library)
Found in HEAD commit: ee765c82cdb8fda389b5b028a35744c8dc2be1a9
Found in base branch: master
Vulnerability Details
ssh2 is client and server modules written in pure JavaScript for node.js. In ssh2 before version 1.4.0 there is a command injection vulnerability. The issue only exists on Windows. This issue may lead to remote code execution if a client of the library calls the vulnerable method with untrusted input. This is fixed in version 1.4.0.
Publish Date: 2021-09-20
URL: CVE-2020-26301
CVSS 3 Score Details (10.0)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: https://securitylab.github.com/advisories/GHSL-2020-123-mscdex-ssh2/
Release Date: 2021-09-20
Fix Resolution: ssh2 - 1.4.0
CVE-2021-37713
Vulnerable Library - tar-0.1.20.tgz
tar for node
Library home page: https://registry.npmjs.org/tar/-/tar-0.1.20.tgz
Path to dependency file: /apps/strider/package.json
Path to vulnerable library: /apps/strider/node_modules/tar/package.json
Dependency Hierarchy:
- strider-ssh-deploy-1.0.0.tgz (Root Library)
- npmd-pack-1.0.0.tgz
- ❌ tar-0.1.20.tgz (Vulnerable Library)
Found in HEAD commit: ee765c82cdb8fda389b5b028a35744c8dc2be1a9
Found in base branch: master
Vulnerability Details
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.
Publish Date: 2021-08-31
URL: CVE-2021-37713
CVSS 3 Score Details (8.6)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: GHSA-5955-9wpr-37jh
Release Date: 2021-08-31
Fix Resolution: tar - 4.4.18,5.0.10,6.1.9
CVE-2021-37712
Vulnerable Library - tar-0.1.20.tgz
tar for node
Library home page: https://registry.npmjs.org/tar/-/tar-0.1.20.tgz
Path to dependency file: /apps/strider/package.json
Path to vulnerable library: /apps/strider/node_modules/tar/package.json
Dependency Hierarchy:
- strider-ssh-deploy-1.0.0.tgz (Root Library)
- npmd-pack-1.0.0.tgz
- ❌ tar-0.1.20.tgz (Vulnerable Library)
Found in HEAD commit: ee765c82cdb8fda389b5b028a35744c8dc2be1a9
Found in base branch: master
Vulnerability Details
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 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 names containing unicode values that normalized to the same value. Additionally, on Windows systems, long path portions would resolve to the same file system entities as their 8.3 "short path" counterparts. A specially crafted tar archive could thus include a directory with one form of the path, followed by a symbolic link with a different string that resolves to the same file system entity, followed by a file using the first form. By first creating a directory, and then replacing that directory with a symlink that had a different apparent name that resolved to the same entry in the filesystem, 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. 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. If this is not possible, a workaround is available in the referenced GHSA-qq89-hq3f-393p.
Publish Date: 2021-08-31
URL: CVE-2021-37712
CVSS 3 Score Details (8.6)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: GHSA-qq89-hq3f-393p
Release Date: 2021-08-31
Fix Resolution: tar - 4.4.18,5.0.10,6.1.9
CVE-2021-37701
Vulnerable Library - tar-0.1.20.tgz
tar for node
Library home page: https://registry.npmjs.org/tar/-/tar-0.1.20.tgz
Path to dependency file: /apps/strider/package.json
Path to vulnerable library: /apps/strider/node_modules/tar/package.json
Dependency Hierarchy:
- strider-ssh-deploy-1.0.0.tgz (Root Library)
- npmd-pack-1.0.0.tgz
- ❌ tar-0.1.20.tgz (Vulnerable Library)
Found in HEAD commit: ee765c82cdb8fda389b5b028a35744c8dc2be1a9
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 at FOO, followed by a symbolic link named foo, 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 the FOO 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:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: GHSA-9r2w-394v-53qc
Release Date: 2021-08-31
Fix Resolution: tar - 4.4.16,5.0.8,6.1.7
CVE-2021-32804
Vulnerable Library - tar-0.1.20.tgz
tar for node
Library home page: https://registry.npmjs.org/tar/-/tar-0.1.20.tgz
Path to dependency file: /apps/strider/package.json
Path to vulnerable library: /apps/strider/node_modules/tar/package.json
Dependency Hierarchy:
- strider-ssh-deploy-1.0.0.tgz (Root Library)
- npmd-pack-1.0.0.tgz
- ❌ tar-0.1.20.tgz (Vulnerable Library)
Found in HEAD commit: ee765c82cdb8fda389b5b028a35744c8dc2be1a9
Found in base branch: master
Vulnerability Details
The npm package "tar" (aka node-tar) before versions 6.1.1, 5.0.6, 4.4.14, and 3.3.2 has a arbitrary File Creation/Overwrite vulnerability due to insufficient absolute path sanitization. node-tar aims to prevent extraction of absolute file paths by turning absolute paths into relative paths when the preservePaths flag is not set to true. This is achieved by stripping the absolute path root from any absolute file paths contained in a tar file. For example /home/user/.bashrc would turn into home/user/.bashrc. This logic was insufficient when file paths contained repeated path roots such as ////home/user/.bashrc. node-tar would only strip a single path root from such paths. When given an absolute file path with repeating path roots, the resulting path (e.g. ///home/user/.bashrc) would still resolve to an absolute path, thus allowing arbitrary file creation and overwrite. This issue was addressed in releases 3.2.2, 4.4.14, 5.0.6 and 6.1.1. Users may work around this vulnerability without upgrading by creating a custom onentry method which sanitizes the entry.path or a filter method which removes entries with absolute paths. See referenced GitHub Advisory for details. Be aware of CVE-2021-32803 which fixes a similar bug in later versions of tar.
Publish Date: 2021-08-03
URL: CVE-2021-32804
CVSS 3 Score Details (8.1)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: GHSA-3jfq-g458-7qm9
Release Date: 2021-08-03
Fix Resolution: tar - 3.2.2, 4.4.14, 5.0.6, 6.1.1
CVE-2021-32803
Vulnerable Library - tar-0.1.20.tgz
tar for node
Library home page: https://registry.npmjs.org/tar/-/tar-0.1.20.tgz
Path to dependency file: /apps/strider/package.json
Path to vulnerable library: /apps/strider/node_modules/tar/package.json
Dependency Hierarchy:
- strider-ssh-deploy-1.0.0.tgz (Root Library)
- npmd-pack-1.0.0.tgz
- ❌ tar-0.1.20.tgz (Vulnerable Library)
Found in HEAD commit: ee765c82cdb8fda389b5b028a35744c8dc2be1a9
Found in base branch: master
Vulnerability Details
The npm package "tar" (aka node-tar) before versions 6.1.2, 5.0.7, 4.4.15, and 3.2.3 has an arbitrary File Creation/Overwrite vulnerability via insufficient symlink protection. 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. This order of operations resulted in the directory being created and added to the node-tar directory cache. When a directory is present in the directory cache, subsequent calls to mkdir for that directory are skipped. However, this is also where node-tar checks for symlinks occur. 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. This issue was addressed in releases 3.2.3, 4.4.15, 5.0.7 and 6.1.2.
Publish Date: 2021-08-03
URL: CVE-2021-32803
CVSS 3 Score Details (8.1)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: GHSA-r628-mhmh-qjhw
Release Date: 2021-08-03
Fix Resolution: tar - 3.2.3, 4.4.15, 5.0.7, 6.1.2
CVE-2018-20834
Vulnerable Library - tar-0.1.20.tgz
tar for node
Library home page: https://registry.npmjs.org/tar/-/tar-0.1.20.tgz
Path to dependency file: /apps/strider/package.json
Path to vulnerable library: /apps/strider/node_modules/tar/package.json
Dependency Hierarchy:
- strider-ssh-deploy-1.0.0.tgz (Root Library)
- npmd-pack-1.0.0.tgz
- ❌ tar-0.1.20.tgz (Vulnerable Library)
Found in HEAD commit: ee765c82cdb8fda389b5b028a35744c8dc2be1a9
Found in base branch: master
Vulnerability Details
A vulnerability was found in node-tar before version 4.4.2 (excluding version 2.2.2). An Arbitrary File Overwrite issue exists when extracting a tarball containing a hardlink to a file that already exists on the system, in conjunction with a later plain file with the same name as the hardlink. This plain file content replaces the existing file content. A patch has been applied to node-tar v2.2.2).
Publish Date: 2019-04-30
URL: CVE-2018-20834
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16082
Release Date: 2019-04-30
Fix Resolution: 2.2.2,4.4.2
CVE-2015-8860
Vulnerable Library - tar-0.1.20.tgz
tar for node
Library home page: https://registry.npmjs.org/tar/-/tar-0.1.20.tgz
Path to dependency file: /apps/strider/package.json
Path to vulnerable library: /apps/strider/node_modules/tar/package.json
Dependency Hierarchy:
- strider-ssh-deploy-1.0.0.tgz (Root Library)
- npmd-pack-1.0.0.tgz
- ❌ tar-0.1.20.tgz (Vulnerable Library)
Found in HEAD commit: ee765c82cdb8fda389b5b028a35744c8dc2be1a9
Found in base branch: master
Vulnerability Details
The tar package before 2.0.0 for Node.js allows remote attackers to write to arbitrary files via a symlink attack in an archive.
Publish Date: 2017-01-23
URL: CVE-2015-8860
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: https://nvd.nist.gov/vuln/detail/CVE-2015-8860
Release Date: 2017-01-23
Fix Resolution: 2.0.0
CVE-2019-13173
Vulnerable Library - fstream-0.1.31.tgz
Advanced file system stream things
Library home page: https://registry.npmjs.org/fstream/-/fstream-0.1.31.tgz
Path to dependency file: /apps/strider/package.json
Path to vulnerable library: /apps/strider/node_modules/tar/node_modules/fstream/package.json
Dependency Hierarchy:
- strider-ssh-deploy-1.0.0.tgz (Root Library)
- npmd-pack-1.0.0.tgz
- tar-0.1.20.tgz
- ❌ fstream-0.1.31.tgz (Vulnerable Library)
Found in HEAD commit: ee765c82cdb8fda389b5b028a35744c8dc2be1a9
Found in base branch: master
Vulnerability Details
fstream before 1.0.12 is vulnerable to Arbitrary File Overwrite. Extracting tarballs containing a hardlink to a file that already exists in the system, and a file that matches the hardlink, will overwrite the system's file with the contents of the extracted file. The fstream.DirWriter() function is vulnerable.
Publish Date: 2019-07-02
URL: CVE-2019-13173
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13173
Release Date: 2020-08-24
Fix Resolution: 1.0.12
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent