LiveActive security incident?Get immediate response
CVE Record

CVE-2020-7701: Prototype Pollution

madlib-object-utils before 0.1.7 is vulnerable to Prototype Pollution via setValue.

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-7701 affects madlib-object-utils before 0.1.7. A flaw in setValue can let untrusted object paths alter shared JavaScript object prototypes. If the package is used in application data handling, this can create integrity, confidentiality, and availability risk depending on how polluted properties are later used.

Executive priority

Prioritize remediation for internet-facing or API-driven applications using this package. The CVSS score is critical, but urgency should be tied to confirmed dependency presence and whether untrusted data reaches vulnerable object assignment logic.

Technical view

The issue is prototype pollution in the madlib-object-utils setValue function. The source bundle assigns CVSS 3.1 score 9.8 with network attack vector, low complexity, no privileges, and no user interaction. Affected version detail is limited to releases before 0.1.7; no CPEs or CWE mapping are provided.

Likely exposure

Exposure is most likely in JavaScript or Node.js applications that directly or transitively include madlib-object-utils before 0.1.7, especially where attacker-controlled keys, paths, or objects reach setValue-like data merging or assignment flows.

Exploitation context

The source bundle marks this CVE as not in KEV, and provides no cited evidence of active exploitation. The CVSS vector indicates theoretical remote, unauthenticated exploitability, but real-world impact depends on application-specific input paths and downstream trust decisions.

Researcher notes

Evidence is narrow: the bundle names prototype pollution via setValue and the fixed boundary before 0.1.7. No exploit details, vulnerable call examples, CPEs, KEV listing, or confirmed exploitation are provided. Validate reachability in application context rather than assuming every dependency occurrence is exploitable.

Mitigation direction

  • Upgrade madlib-object-utils to version 0.1.7 or later where the package is present.
  • Check direct and transitive dependency manifests for vulnerable madlib-object-utils versions.
  • If upgrade is delayed, restrict untrusted input from reaching object path assignment logic.
  • Review vendor and package advisory guidance before relying on compensating controls.

Validation and detection

  • Inventory applications and services using madlib-object-utils before 0.1.7.
  • Confirm lockfiles or package metadata resolve madlib-object-utils to 0.1.7 or later.
  • Trace whether attacker-controlled keys or paths can reach setValue usage.
  • Regression-test affected data handling after dependency upgrade.
Prepared
Confidence
medium
Sources
3

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-7701 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
2Source 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-7701Attack 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/amadlib-object-utilsunspecifiedListed
Weakness

CWE details

No CWE listed

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