Repository navigation
CVE-2020-7720 (High) detected in node-forge-0.9.0.tgz #81
Description
CVE-2020-7720 - High Severity Vulnerability
Vulnerable Library - node-forge-0.9.0.tgz
JavaScript implementations of network transports, cryptography, ciphers, PKI, message digests, and various utilities.
Library home page: https://registry.npmjs.org/node-forge/-/node-forge-0.9.0.tgz
Path to dependency file: /deps/npm/docs/package.json
Path to vulnerable library: /deps/npm/docs/package.json
Dependency Hierarchy:
- gatsby-2.23.20.tgz (Root Library)
- webpack-dev-server-3.11.0.tgz
- selfsigned-1.10.7.tgz
- ❌ node-forge-0.9.0.tgz (Vulnerable Library)
- selfsigned-1.10.7.tgz
- webpack-dev-server-3.11.0.tgz
Found in HEAD commit: 00fdb00d5bdbaea4fec4642989374d82cbdb1a3c
Found in base branch: master
Vulnerability Details
The package node-forge before 0.10.0 is vulnerable to Prototype Pollution via the util.setPath function. Note: Version 0.10.0 is a breaking change removing the vulnerable functions.
Publish Date: 2020-09-01
URL: CVE-2020-7720
CVSS 3 Score Details (7.3)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
Suggested Fix
Type: Upgrade version
Release Date: 2020-09-01
Fix Resolution (node-forge): 0.10.0
Direct dependency fix Resolution (gatsby): 2.23.21-oom-exit-code.13
Step up your Open Source Security Game with Mend here
Activity
[-]CVE-2020-7720 (High) detected in node-forge-0.9.0.tgz[/-][+]CVE-2020-7720 (High) detected in node-forge-0.9.0.tgz - autoclosed[/+]mend-bolt-for-github commentedon Mar 31, 2021
✔️ This issue was automatically closed by WhiteSource because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the WhiteSource inventory.
[-]CVE-2020-7720 (High) detected in node-forge-0.9.0.tgz - autoclosed[/-][+]CVE-2020-7720 (High) detected in node-forge-0.9.0.tgz[/+][-]CVE-2020-7720 (High) detected in node-forge-0.9.0.tgz - autoclosed[/-][+]CVE-2020-7720 (High) detected in node-forge-0.9.0.tgz[/+][-]CVE-2020-7720 (High) detected in node-forge-0.9.0.tgz - autoclosed[/-][+]CVE-2020-7720 (High) detected in node-forge-0.9.0.tgz[/+][-]CVE-2020-7720 (High) detected in node-forge-0.9.0.tgz - autoclosed[/-][+]CVE-2020-7720 (High) detected in node-forge-0.9.0.tgz[/+][-]CVE-2020-7720 (High) detected in node-forge-0.9.0.tgz - autoclosed[/-][+]CVE-2020-7720 (High) detected in node-forge-0.9.0.tgz[/+]mend-bolt-for-github commentedon 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.
mend-bolt-for-github commentedon 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.
mend-bolt-for-github commentedon 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.
mend-bolt-for-github commentedon 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.
mend-bolt-for-github commentedon 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.
[-]CVE-2020-7720 (High) detected in node-forge-0.9.0.tgz[/-][+]CVE-2020-7720 (High) detected in node-forge-0.9.0.tgz - autoclosed[/+]mend-bolt-for-github commentedon Apr 21, 2023
✔️ 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.
[-]CVE-2020-7720 (High) detected in node-forge-0.9.0.tgz - autoclosed[/-][+]CVE-2020-7720 (High) detected in node-forge-0.9.0.tgz[/+]mend-bolt-for-github commentedon Apr 26, 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.