LiveActive security incident?Get immediate response
CVE Record

CVE-2020-7720: Prototype Pollution

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.

CriticalCVSS 9.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2020-7720 affects node-forge before 0.10.0. A vulnerable helper could let untrusted input alter JavaScript object prototypes, potentially changing application behavior or security decisions. The published score is critical, but the provided sources do not show active exploitation.

Executive priority

Treat as high-priority remediation for internet-facing or input-processing applications. The severity is critical, but urgency should be based on confirmed dependency presence and reachable vulnerable code paths.

Technical view

The issue is prototype pollution in node-forge util.setPath before version 0.10.0. The CVSS 3.1 score is 9.8 with network attack vector and no privileges or user interaction required. Version 0.10.0 is described as a breaking change that removes the vulnerable functions.

Likely exposure

Exposure is most likely in JavaScript applications, Node.js services, or bundled dependencies using node-forge versions before 0.10.0. Risk depends on whether attacker-controlled data can reach util.setPath or dependent code paths.

Exploitation context

The bundle marks KEV as false, so there is no provided evidence of known active exploitation. The CVSS temporal vector indicates proof-of-concept maturity, but no exploit details should be assumed beyond the cited advisory data.

Researcher notes

Evidence identifies node-forge before 0.10.0 and the vulnerable util.setPath function. The sources do not provide active exploitation evidence. Validate reachability before escalating beyond dependency remediation, especially where node-forge is only present transitively.

Mitigation direction

  • Upgrade node-forge to 0.10.0 or later where feasible.
  • Plan compatibility testing because 0.10.0 is described as a breaking change.
  • Check vendor and dependency guidance for transitive package paths.
  • Prioritize services that process untrusted external input.
  • Remove or isolate code paths using vulnerable helper behavior.

Validation and detection

  • Inventory package manifests, lockfiles, and SBOMs for node-forge versions before 0.10.0.
  • Identify transitive dependencies that bundle node-forge.
  • Review whether untrusted input reaches util.setPath-related code paths.
  • Confirm upgraded builds no longer resolve vulnerable node-forge versions.
  • Run regression tests around crypto, certificate, and encoding workflows using node-forge.
Prepared
Confidence
high
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2020-7720 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2020-7720Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/anode-forge0Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.