📂 Vulnerable Library - bcrypt-1.0.3.tgz
A bcrypt library for NodeJS.
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/bcrypt/package.json
Findings
| Finding |
Severity |
🎯 CVSS |
Exploit Maturity |
EPSS |
Library |
Type |
Fixed in |
Remediation Available |
Reachability |
| CVE-289561-266276 |
🟣 Critical |
9.8 |
N/A |
N/A |
inherits-2.0.4.tgz |
Transitive |
N/A |
❌ |
|
| CVE-295712-399081 |
🟣 Critical |
9.8 |
N/A |
N/A |
asn1-0.2.6.tgz |
Transitive |
N/A |
❌ |
|
| CVE-495493-603164 |
🟣 Critical |
9.8 |
N/A |
N/A |
delegates-1.0.0.tgz |
Transitive |
N/A |
❌ |
|
| CVE-72435-185255 |
🟣 Critical |
9.8 |
N/A |
N/A |
tweetnacl-0.14.5.tgz |
Transitive |
N/A |
❌ |
|
| CVE-814504-1548 |
🟣 Critical |
9.8 |
N/A |
N/A |
isstream-0.1.2.tgz |
Transitive |
N/A |
❌ |
|
| CVE-893166-217151 |
🟣 Critical |
9.8 |
N/A |
N/A |
form-data-2.3.3.tgz |
Transitive |
N/A |
❌ |
|
| CVE-2025-7783 |
🟣 Critical |
9.4 |
Not Defined |
< 1% |
form-data-2.3.3.tgz |
Transitive |
N/A |
❌ |
 Unreachable |
| CVE-2021-32803 |
🟣 Critical |
9.2 |
Not Defined |
< 1% |
tar-2.2.2.tgz |
Transitive |
N/A |
❌ |
Unreachable |
| CVE-2021-32804 |
🟣 Critical |
9.2 |
Not Defined |
85.5% |
tar-2.2.2.tgz |
Transitive |
N/A |
❌ |
Unreachable |
| CVE-2021-37701 |
🟣 Critical |
9.2 |
Not Defined |
< 1% |
tar-2.2.2.tgz |
Transitive |
N/A |
❌ |
Unreachable |
| CVE-2021-37712 |
🟣 Critical |
9.2 |
Not Defined |
< 1% |
tar-2.2.2.tgz |
Transitive |
N/A |
❌ |
Unreachable |
| CVE-2021-37713 |
🟣 Critical |
9.2 |
Not Defined |
< 1% |
tar-2.2.2.tgz |
Transitive |
N/A |
❌ |
Unreachable |
| CVE-2020-7689 |
🔴 High |
8.2 |
Not Defined |
< 1% |
bcrypt-1.0.3.tgz |
Direct |
bcrypt - 5.0.0,https://github.com/kelektiv/node.bcrypt.js.git - no_fix |
✅ |
 Reachable |
| CVE-2023-28155 |
🟠 Medium |
5.3 |
Not Defined |
< 1% |
request-2.88.2.tgz |
Transitive |
N/A |
❌ |
Unreachable |
Details
🟣CVE-289561-266276
Vulnerable Library - inherits-2.0.4.tgz
Browser-friendly inheritance fully compatible with standard node.js inherits()
Library home page: https://registry.npmjs.org/inherits/-/inherits-2.0.4.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/inherits/package.json
Dependency Hierarchy:
-
csurf-1.11.0.tgz (Root Library)
- http-errors-1.7.3.tgz
- ❌ inherits-2.0.4.tgz (Vulnerable Library)
-
libxmljs-0.19.10.tgz (Root Library)
- node-pre-gyp-1.0.11.tgz
- npmlog-5.0.1.tgz
- are-we-there-yet-2.0.0.tgz
- readable-stream-3.6.2.tgz
- ❌ inherits-2.0.4.tgz (Vulnerable Library)
-
bcrypt-1.0.3.tgz (Root Library)
- node-pre-gyp-0.6.36.tgz
- tar-pack-3.4.1.tgz
- readable-stream-2.3.8.tgz
- ❌ inherits-2.0.4.tgz (Vulnerable Library)
-
express-fileupload-0.4.0.tgz (Root Library)
- busboy-0.2.14.tgz
- readable-stream-1.1.14.tgz
- ❌ inherits-2.0.4.tgz (Vulnerable Library)
-
express-4.21.2.tgz (Root Library)
- send-0.19.0.tgz
- http-errors-2.0.0.tgz
- ❌ inherits-2.0.4.tgz (Vulnerable Library)
-
winston-3.18.3.tgz (Root Library)
- winston-transport-4.9.0.tgz
- readable-stream-3.6.2.tgz
- ❌ inherits-2.0.4.tgz (Vulnerable Library)
Vulnerability Details
Created automatically by the test suite
Publish Date: Jun 07, 2010 05:12 PM
URL: CVE-289561-266276
Threat Assessment
Exploit Maturity:N/A
EPSS:N/A
Score: 9.8
Suggested Fix
Type: Upgrade version
Origin:
Release Date:
Fix Resolution :
🟣CVE-295712-399081
Vulnerable Library - asn1-0.2.6.tgz
Contains parsers and serializers for ASN.1 (currently BER only)
Library home page: https://registry.npmjs.org/asn1/-/asn1-0.2.6.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/asn1/package.json
Dependency Hierarchy:
- bcrypt-1.0.3.tgz (Root Library)
- node-pre-gyp-0.6.36.tgz
- request-2.88.2.tgz
- http-signature-1.2.0.tgz
- sshpk-1.18.0.tgz
- ❌ asn1-0.2.6.tgz (Vulnerable Library)
Vulnerability Details
Created automatically by the test suite
Publish Date: Jun 07, 2010 05:12 PM
URL: CVE-295712-399081
Threat Assessment
Exploit Maturity:N/A
EPSS:N/A
Score: 9.8
Suggested Fix
Type: Upgrade version
Origin:
Release Date:
Fix Resolution :
🟣CVE-495493-603164
Vulnerable Library - delegates-1.0.0.tgz
delegate methods and accessors to another property
Library home page: https://registry.npmjs.org/delegates/-/delegates-1.0.0.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/delegates/package.json
Dependency Hierarchy:
Vulnerability Details
Created automatically by the test suite
Publish Date: Jun 07, 2010 05:12 PM
URL: CVE-495493-603164
Threat Assessment
Exploit Maturity:N/A
EPSS:N/A
Score: 9.8
Suggested Fix
Type: Upgrade version
Origin:
Release Date:
Fix Resolution :
🟣CVE-72435-185255
Vulnerable Library - tweetnacl-0.14.5.tgz
Port of TweetNaCl cryptographic library to JavaScript
Library home page: https://registry.npmjs.org/tweetnacl/-/tweetnacl-0.14.5.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/tweetnacl/package.json
Dependency Hierarchy:
- bcrypt-1.0.3.tgz (Root Library)
- node-pre-gyp-0.6.36.tgz
- request-2.88.2.tgz
- http-signature-1.2.0.tgz
- sshpk-1.18.0.tgz
- bcrypt-pbkdf-1.0.2.tgz
- ❌ tweetnacl-0.14.5.tgz (Vulnerable Library)
Vulnerability Details
Created automatically by the test suite
Publish Date: Jun 07, 2010 05:12 PM
URL: CVE-72435-185255
Threat Assessment
Exploit Maturity:N/A
EPSS:N/A
Score: 9.8
Suggested Fix
Type: Upgrade version
Origin:
Release Date:
Fix Resolution :
🟣CVE-814504-1548
Vulnerable Library - isstream-0.1.2.tgz
Determine if an object is a Stream
Library home page: https://registry.npmjs.org/isstream/-/isstream-0.1.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/isstream/package.json
Dependency Hierarchy:
- bcrypt-1.0.3.tgz (Root Library)
- node-pre-gyp-0.6.36.tgz
- request-2.88.2.tgz
- ❌ isstream-0.1.2.tgz (Vulnerable Library)
Vulnerability Details
Created automatically by the test suite
Publish Date: Jun 07, 2010 05:12 PM
URL: CVE-814504-1548
Threat Assessment
Exploit Maturity:N/A
EPSS:N/A
Score: 9.8
Suggested Fix
Type: Upgrade version
Origin:
Release Date:
Fix Resolution :
🟣CVE-893166-217151
Vulnerable Library - form-data-2.3.3.tgz
A library to create readable "multipart/form-data" streams. Can be used to submit forms and file uploads to other web applications.
Library home page: https://registry.npmjs.org/form-data/-/form-data-2.3.3.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/form-data/package.json
Dependency Hierarchy:
- bcrypt-1.0.3.tgz (Root Library)
- node-pre-gyp-0.6.36.tgz
- request-2.88.2.tgz
- ❌ form-data-2.3.3.tgz (Vulnerable Library)
Vulnerability Details
Created automatically by the test suite
Publish Date: Jun 07, 2010 05:12 PM
URL: CVE-893166-217151
Threat Assessment
Exploit Maturity:N/A
EPSS:N/A
Score: 9.8
Suggested Fix
Type: Upgrade version
Origin:
Release Date:
Fix Resolution :
🟣CVE-2025-7783
Vulnerable Library - form-data-2.3.3.tgz
A library to create readable "multipart/form-data" streams. Can be used to submit forms and file uploads to other web applications.
Library home page: https://registry.npmjs.org/form-data/-/form-data-2.3.3.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/form-data/package.json
Dependency Hierarchy:
- bcrypt-1.0.3.tgz (Root Library)
- node-pre-gyp-0.6.36.tgz
- request-2.88.2.tgz
- ❌ form-data-2.3.3.tgz (Vulnerable Library)
Reachability Analysis
The vulnerable code is unreachable
Vulnerability Details
Use of Insufficiently Random Values vulnerability in form-data allows HTTP Parameter Pollution (HPP). This vulnerability is associated with program files lib/form_data.Js.
This issue affects form-data: < 2.5.4, 3.0.0 - 3.0.3, 4.0.0 - 4.0.3.
Mend Note: The description of this vulnerability differs from MITRE.
Publish Date: Jul 18, 2025 04:34 PM
URL: CVE-2025-7783
Threat Assessment
Exploit Maturity:Not Defined
EPSS:< 1%
Score: 9.4
Suggested Fix
Type: Upgrade version
Origin:
Release Date:
Fix Resolution :
🟣CVE-2021-32803
Vulnerable Library - tar-2.2.2.tgz
tar for node
Library home page: https://registry.npmjs.org/tar/-/tar-2.2.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/tar-pack/node_modules/tar/package.json
Dependency Hierarchy:
- bcrypt-1.0.3.tgz (Root Library)
- node-pre-gyp-0.6.36.tgz
- tar-pack-3.4.1.tgz
- ❌ tar-2.2.2.tgz (Vulnerable Library)
Reachability Analysis
The vulnerable code is unreachable
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.
Mend Note: The description of this vulnerability differs from MITRE.
Publish Date: Aug 03, 2021 07:05 PM
URL: CVE-2021-32803
Threat Assessment
Exploit Maturity:Not Defined
EPSS:< 1%
Score: 9.2
Suggested Fix
Type: Upgrade version
Origin: GHSA-r628-mhmh-qjhw
Release Date: Aug 03, 2021 07:05 PM
Fix Resolution : tar - 6.1.2,tar - 4.4.15,tar - 3.2.3,tar - 5.0.7
🟣CVE-2021-32804
Vulnerable Library - tar-2.2.2.tgz
tar for node
Library home page: https://registry.npmjs.org/tar/-/tar-2.2.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/tar-pack/node_modules/tar/package.json
Dependency Hierarchy:
- bcrypt-1.0.3.tgz (Root Library)
- node-pre-gyp-0.6.36.tgz
- tar-pack-3.4.1.tgz
- ❌ tar-2.2.2.tgz (Vulnerable Library)
Reachability Analysis
The vulnerable code is unreachable
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.
Mend Note: The description of this vulnerability differs from MITRE.
Publish Date: Aug 03, 2021 07:10 PM
URL: CVE-2021-32804
Threat Assessment
Exploit Maturity:Not Defined
EPSS:85.5%
Score: 9.2
Suggested Fix
Type: Upgrade version
Origin: GHSA-3jfq-g458-7qm9
Release Date: Aug 03, 2021 07:10 PM
Fix Resolution : tar - 4.4.14,tar - 6.1.1,tar - 3.2.2,tar - 5.0.6
🟣CVE-2021-37701
Vulnerable Library - tar-2.2.2.tgz
tar for node
Library home page: https://registry.npmjs.org/tar/-/tar-2.2.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/tar-pack/node_modules/tar/package.json
Dependency Hierarchy:
- bcrypt-1.0.3.tgz (Root Library)
- node-pre-gyp-0.6.36.tgz
- tar-pack-3.4.1.tgz
- ❌ tar-2.2.2.tgz (Vulnerable Library)
Reachability Analysis
The vulnerable code is unreachable
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.
Mend Note: The description of this vulnerability differs from MITRE.
Publish Date: Aug 31, 2021 12:00 AM
URL: CVE-2021-37701
Threat Assessment
Exploit Maturity:Not Defined
EPSS:< 1%
Score: 9.2
Suggested Fix
Type: Upgrade version
Origin: GHSA-9r2w-394v-53qc
Release Date: Aug 31, 2021 12:00 AM
Fix Resolution : tar - 5.0.8,tar - 4.4.16,tar - 6.1.7
🟣CVE-2021-37712
Vulnerable Library - tar-2.2.2.tgz
tar for node
Library home page: https://registry.npmjs.org/tar/-/tar-2.2.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/tar-pack/node_modules/tar/package.json
Dependency Hierarchy:
- bcrypt-1.0.3.tgz (Root Library)
- node-pre-gyp-0.6.36.tgz
- tar-pack-3.4.1.tgz
- ❌ tar-2.2.2.tgz (Vulnerable Library)
Reachability Analysis
The vulnerable code is unreachable
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: Aug 31, 2021 12:00 AM
URL: CVE-2021-37712
Threat Assessment
Exploit Maturity:Not Defined
EPSS:< 1%
Score: 9.2
Suggested Fix
Type: Upgrade version
Origin: GHSA-qq89-hq3f-393p
Release Date: Aug 31, 2021 12:00 AM
Fix Resolution : tar - 5.0.10,tar - 6.1.9,tar - 4.4.18
🟣CVE-2021-37713
Vulnerable Library - tar-2.2.2.tgz
tar for node
Library home page: https://registry.npmjs.org/tar/-/tar-2.2.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/tar-pack/node_modules/tar/package.json
Dependency Hierarchy:
- bcrypt-1.0.3.tgz (Root Library)
- node-pre-gyp-0.6.36.tgz
- tar-pack-3.4.1.tgz
- ❌ tar-2.2.2.tgz (Vulnerable Library)
Reachability Analysis
The vulnerable code is unreachable
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.
Mend Note: The description of this vulnerability differs from MITRE.
Publish Date: Aug 31, 2021 04:50 PM
URL: CVE-2021-37713
Threat Assessment
Exploit Maturity:Not Defined
EPSS:< 1%
Score: 9.2
Suggested Fix
Type: Upgrade version
Origin: GHSA-5955-9wpr-37jh
Release Date: Aug 31, 2021 04:50 PM
Fix Resolution : tar - 6.1.9,tar - 5.0.10,tar - 4.4.18
🔴CVE-2020-7689
Vulnerable Library - bcrypt-1.0.3.tgz
A bcrypt library for NodeJS.
Library home page: https://registry.npmjs.org/bcrypt/-/bcrypt-1.0.3.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/bcrypt/package.json
Dependency Hierarchy:
- ❌ bcrypt-1.0.3.tgz (Vulnerable Library)
Reachability Analysis
This vulnerability is potentially reachable:
- dvna-0.0.1/core/authHandler.js (Application)
-> ❌ bcrypt-1.0.3/bcrypt.js (Vulnerable Component)
Vulnerability Details
Data is truncated wrong when its length is greater than 255 bytes.
Publish Date: Jul 01, 2020 01:55 PM
URL: CVE-2020-7689
Threat Assessment
Exploit Maturity:Not Defined
EPSS:< 1%
Score: 8.2
Suggested Fix
Type: Upgrade version
Origin: GHSA-5wg4-74h6-q47v
Release Date: Jul 01, 2020 01:55 PM
Fix Resolution : bcrypt - 5.0.0,https://github.com/kelektiv/node.bcrypt.js.git - no_fix
🟠CVE-2023-28155
Vulnerable Library - request-2.88.2.tgz
Simplified HTTP request client.
Library home page: https://registry.npmjs.org/request/-/request-2.88.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/request/package.json
Dependency Hierarchy:
- bcrypt-1.0.3.tgz (Root Library)
- node-pre-gyp-0.6.36.tgz
- ❌ request-2.88.2.tgz (Vulnerable Library)
Reachability Analysis
The vulnerable code is unreachable
Vulnerability Details
The Request package through 2.88.1 for Node.js allows a bypass of SSRF mitigations via an attacker-controller server that does a cross-protocol redirect (HTTP to HTTPS, or HTTPS to HTTP). NOTE: This vulnerability only affects products that are no longer supported by the maintainer.
Publish Date: Mar 16, 2023 12:00 AM
URL: CVE-2023-28155
Threat Assessment
Exploit Maturity:Not Defined
EPSS:< 1%
Score: 5.3
Suggested Fix
Type: Upgrade version
Origin: GHSA-p8p7-x288-28g6
Release Date: Mar 16, 2023 12:00 AM
Fix Resolution : @cypress/request - 3.0.0
📂 Vulnerable Library - bcrypt-1.0.3.tgz
A bcrypt library for NodeJS.
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/bcrypt/package.json
Findings
Details
🟣CVE-289561-266276
Vulnerable Library - inherits-2.0.4.tgz
Browser-friendly inheritance fully compatible with standard node.js inherits()
Library home page: https://registry.npmjs.org/inherits/-/inherits-2.0.4.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/inherits/package.json
Dependency Hierarchy:
csurf-1.11.0.tgz (Root Library)
libxmljs-0.19.10.tgz (Root Library)
bcrypt-1.0.3.tgz (Root Library)
express-fileupload-0.4.0.tgz (Root Library)
express-4.21.2.tgz (Root Library)
winston-3.18.3.tgz (Root Library)
Vulnerability Details
Created automatically by the test suite
Publish Date: Jun 07, 2010 05:12 PM
URL: CVE-289561-266276
Threat Assessment
Exploit Maturity:N/A
EPSS:N/A
Score: 9.8
Suggested Fix
Type: Upgrade version
Origin:
Release Date:
Fix Resolution :
🟣CVE-295712-399081
Vulnerable Library - asn1-0.2.6.tgz
Contains parsers and serializers for ASN.1 (currently BER only)
Library home page: https://registry.npmjs.org/asn1/-/asn1-0.2.6.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/asn1/package.json
Dependency Hierarchy:
Vulnerability Details
Created automatically by the test suite
Publish Date: Jun 07, 2010 05:12 PM
URL: CVE-295712-399081
Threat Assessment
Exploit Maturity:N/A
EPSS:N/A
Score: 9.8
Suggested Fix
Type: Upgrade version
Origin:
Release Date:
Fix Resolution :
🟣CVE-495493-603164
Vulnerable Library - delegates-1.0.0.tgz
delegate methods and accessors to another property
Library home page: https://registry.npmjs.org/delegates/-/delegates-1.0.0.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/delegates/package.json
Dependency Hierarchy:
libxmljs-0.19.10.tgz (Root Library)
bcrypt-1.0.3.tgz (Root Library)
Vulnerability Details
Created automatically by the test suite
Publish Date: Jun 07, 2010 05:12 PM
URL: CVE-495493-603164
Threat Assessment
Exploit Maturity:N/A
EPSS:N/A
Score: 9.8
Suggested Fix
Type: Upgrade version
Origin:
Release Date:
Fix Resolution :
🟣CVE-72435-185255
Vulnerable Library - tweetnacl-0.14.5.tgz
Port of TweetNaCl cryptographic library to JavaScript
Library home page: https://registry.npmjs.org/tweetnacl/-/tweetnacl-0.14.5.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/tweetnacl/package.json
Dependency Hierarchy:
Vulnerability Details
Created automatically by the test suite
Publish Date: Jun 07, 2010 05:12 PM
URL: CVE-72435-185255
Threat Assessment
Exploit Maturity:N/A
EPSS:N/A
Score: 9.8
Suggested Fix
Type: Upgrade version
Origin:
Release Date:
Fix Resolution :
🟣CVE-814504-1548
Vulnerable Library - isstream-0.1.2.tgz
Determine if an object is a Stream
Library home page: https://registry.npmjs.org/isstream/-/isstream-0.1.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/isstream/package.json
Dependency Hierarchy:
Vulnerability Details
Created automatically by the test suite
Publish Date: Jun 07, 2010 05:12 PM
URL: CVE-814504-1548
Threat Assessment
Exploit Maturity:N/A
EPSS:N/A
Score: 9.8
Suggested Fix
Type: Upgrade version
Origin:
Release Date:
Fix Resolution :
🟣CVE-893166-217151
Vulnerable Library - form-data-2.3.3.tgz
A library to create readable "multipart/form-data" streams. Can be used to submit forms and file uploads to other web applications.
Library home page: https://registry.npmjs.org/form-data/-/form-data-2.3.3.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/form-data/package.json
Dependency Hierarchy:
Vulnerability Details
Created automatically by the test suite
Publish Date: Jun 07, 2010 05:12 PM
URL: CVE-893166-217151
Threat Assessment
Exploit Maturity:N/A
EPSS:N/A
Score: 9.8
Suggested Fix
Type: Upgrade version
Origin:
Release Date:
Fix Resolution :
🟣CVE-2025-7783
Vulnerable Library - form-data-2.3.3.tgz
A library to create readable "multipart/form-data" streams. Can be used to submit forms and file uploads to other web applications.
Library home page: https://registry.npmjs.org/form-data/-/form-data-2.3.3.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/form-data/package.json
Dependency Hierarchy:
Reachability Analysis
The vulnerable code is unreachable
Vulnerability Details
Use of Insufficiently Random Values vulnerability in form-data allows HTTP Parameter Pollution (HPP). This vulnerability is associated with program files lib/form_data.Js.
This issue affects form-data: < 2.5.4, 3.0.0 - 3.0.3, 4.0.0 - 4.0.3.
Mend Note: The description of this vulnerability differs from MITRE.
Publish Date: Jul 18, 2025 04:34 PM
URL: CVE-2025-7783
Threat Assessment
Exploit Maturity:Not Defined
EPSS:< 1%
Score: 9.4
Suggested Fix
Type: Upgrade version
Origin:
Release Date:
Fix Resolution :
🟣CVE-2021-32803
Vulnerable Library - tar-2.2.2.tgz
tar for node
Library home page: https://registry.npmjs.org/tar/-/tar-2.2.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/tar-pack/node_modules/tar/package.json
Dependency Hierarchy:
Reachability Analysis
The vulnerable code is unreachable
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.
Mend Note: The description of this vulnerability differs from MITRE.
Publish Date: Aug 03, 2021 07:05 PM
URL: CVE-2021-32803
Threat Assessment
Exploit Maturity:Not Defined
EPSS:< 1%
Score: 9.2
Suggested Fix
Type: Upgrade version
Origin: GHSA-r628-mhmh-qjhw
Release Date: Aug 03, 2021 07:05 PM
Fix Resolution : tar - 6.1.2,tar - 4.4.15,tar - 3.2.3,tar - 5.0.7
🟣CVE-2021-32804
Vulnerable Library - tar-2.2.2.tgz
tar for node
Library home page: https://registry.npmjs.org/tar/-/tar-2.2.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/tar-pack/node_modules/tar/package.json
Dependency Hierarchy:
Reachability Analysis
The vulnerable code is unreachable
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.
Mend Note: The description of this vulnerability differs from MITRE.
Publish Date: Aug 03, 2021 07:10 PM
URL: CVE-2021-32804
Threat Assessment
Exploit Maturity:Not Defined
EPSS:85.5%
Score: 9.2
Suggested Fix
Type: Upgrade version
Origin: GHSA-3jfq-g458-7qm9
Release Date: Aug 03, 2021 07:10 PM
Fix Resolution : tar - 4.4.14,tar - 6.1.1,tar - 3.2.2,tar - 5.0.6
🟣CVE-2021-37701
Vulnerable Library - tar-2.2.2.tgz
tar for node
Library home page: https://registry.npmjs.org/tar/-/tar-2.2.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/tar-pack/node_modules/tar/package.json
Dependency Hierarchy:
Reachability Analysis
The vulnerable code is unreachable
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.
Mend Note: The description of this vulnerability differs from MITRE.
Publish Date: Aug 31, 2021 12:00 AM
URL: CVE-2021-37701
Threat Assessment
Exploit Maturity:Not Defined
EPSS:< 1%
Score: 9.2
Suggested Fix
Type: Upgrade version
Origin: GHSA-9r2w-394v-53qc
Release Date: Aug 31, 2021 12:00 AM
Fix Resolution : tar - 5.0.8,tar - 4.4.16,tar - 6.1.7
🟣CVE-2021-37712
Vulnerable Library - tar-2.2.2.tgz
tar for node
Library home page: https://registry.npmjs.org/tar/-/tar-2.2.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/tar-pack/node_modules/tar/package.json
Dependency Hierarchy:
Reachability Analysis
The vulnerable code is unreachable
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: Aug 31, 2021 12:00 AM
URL: CVE-2021-37712
Threat Assessment
Exploit Maturity:Not Defined
EPSS:< 1%
Score: 9.2
Suggested Fix
Type: Upgrade version
Origin: GHSA-qq89-hq3f-393p
Release Date: Aug 31, 2021 12:00 AM
Fix Resolution : tar - 5.0.10,tar - 6.1.9,tar - 4.4.18
🟣CVE-2021-37713
Vulnerable Library - tar-2.2.2.tgz
tar for node
Library home page: https://registry.npmjs.org/tar/-/tar-2.2.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/tar-pack/node_modules/tar/package.json
Dependency Hierarchy:
Reachability Analysis
The vulnerable code is unreachable
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.
Mend Note: The description of this vulnerability differs from MITRE.
Publish Date: Aug 31, 2021 04:50 PM
URL: CVE-2021-37713
Threat Assessment
Exploit Maturity:Not Defined
EPSS:< 1%
Score: 9.2
Suggested Fix
Type: Upgrade version
Origin: GHSA-5955-9wpr-37jh
Release Date: Aug 31, 2021 04:50 PM
Fix Resolution : tar - 6.1.9,tar - 5.0.10,tar - 4.4.18
🔴CVE-2020-7689
Vulnerable Library - bcrypt-1.0.3.tgz
A bcrypt library for NodeJS.
Library home page: https://registry.npmjs.org/bcrypt/-/bcrypt-1.0.3.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/bcrypt/package.json
Dependency Hierarchy:
Reachability Analysis
This vulnerability is potentially reachable:
Vulnerability Details
Data is truncated wrong when its length is greater than 255 bytes.
Publish Date: Jul 01, 2020 01:55 PM
URL: CVE-2020-7689
Threat Assessment
Exploit Maturity:Not Defined
EPSS:< 1%
Score: 8.2
Suggested Fix
Type: Upgrade version
Origin: GHSA-5wg4-74h6-q47v
Release Date: Jul 01, 2020 01:55 PM
Fix Resolution : bcrypt - 5.0.0,https://github.com/kelektiv/node.bcrypt.js.git - no_fix
🟠CVE-2023-28155
Vulnerable Library - request-2.88.2.tgz
Simplified HTTP request client.
Library home page: https://registry.npmjs.org/request/-/request-2.88.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/request/package.json
Dependency Hierarchy:
Reachability Analysis
The vulnerable code is unreachable
Vulnerability Details
The Request package through 2.88.1 for Node.js allows a bypass of SSRF mitigations via an attacker-controller server that does a cross-protocol redirect (HTTP to HTTPS, or HTTPS to HTTP). NOTE: This vulnerability only affects products that are no longer supported by the maintainer.
Publish Date: Mar 16, 2023 12:00 AM
URL: CVE-2023-28155
Threat Assessment
Exploit Maturity:Not Defined
EPSS:< 1%
Score: 5.3
Suggested Fix
Type: Upgrade version
Origin: GHSA-p8p7-x288-28g6
Release Date: Mar 16, 2023 12:00 AM
Fix Resolution : @cypress/request - 3.0.0