LiveActive security incident?Get immediate response
CVE Record

CVE-2020-7770: Prototype Pollution

This affects the package json8 before 1.0.3. The function adds in the target object the property specified in the path, however it does not properly check the key being set, leading to a prototype pollution.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

json8 versions before 1.0.3 can let untrusted path data alter JavaScript object prototypes. In business terms, affected applications may make unsafe assumptions about object properties, with the CVSS vector indicating possible high confidentiality impact. Urgency is moderate unless json8 processes untrusted user-controlled paths in exposed workflows.

Executive priority

Treat as a moderate dependency remediation. It is not known exploited from the provided evidence, but prototype pollution can create hard-to-predict application behavior. Prioritize systems where json8 handles external input or sensitive data transformations.

Technical view

CVE-2020-7770 is prototype pollution in the json8 package before 1.0.3. The affected function adds a property to a target object from a supplied path but does not properly reject unsafe keys. The published CVSS 3.1 score is 6.5, network reachable, low complexity, no privileges required, user interaction required, and high confidentiality impact.

Likely exposure

Exposure is limited to JavaScript applications that use json8 before 1.0.3, directly or transitively, especially where path input can be influenced by users or external data. The source bundle does not identify specific downstream products, platforms, or hosted services.

Exploitation context

The provided sources do not show CISA KEV listing or cited active exploitation. Exploitability depends on whether an application passes untrusted path values into the vulnerable json8 function and whether polluted prototype state can influence sensitive logic.

Researcher notes

The source evidence names json8 before 1.0.3 and describes insufficient key validation during path-based property assignment. No CWE is listed in the bundle. Do not assume remote code execution or availability impact from these sources alone; the CVSS vector emphasizes confidentiality impact with required user interaction.

Mitigation direction

  • Upgrade json8 to version 1.0.3 or later.
  • Check direct and transitive dependencies for json8 before 1.0.3.
  • Review vendor advisory and patch commit before release approval.
  • Prioritize exposed workflows that process user-controlled JSON paths.
  • Run regression tests around affected JSON object handling.

Validation and detection

  • Confirm production dependency inventory includes no json8 version before 1.0.3.
  • Verify lockfiles and deployed artifacts match the remediated version.
  • Identify code paths passing external path values into json8.
  • Review SCA results for CVE-2020-7770 closure.
  • Test relevant workflows for unexpected inherited object properties.
Prepared
Confidence
medium
Sources
4

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-7770 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
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

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
3Source 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
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2020-7770Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

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/ajson8unspecifiedListed
Weakness

CWE details

No CWE listed

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