LiveActive security incident?Get immediate response
CVE Record

CVE-2020-7766: Prototype Pollution

This affects all versions of package json-ptr. The issue occurs in the set operation (https://flitbit.github.io/json-ptr/classes/_src_pointer_.jsonpointer.htmlset) when the force flag is set to true. The function recursively set the property in the target object, however it does not properly check the key being set, leading to a prototype pollution.

HighCVSS 7.3Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-7766 is a high-severity prototype pollution flaw in the json-ptr package. If an application lets untrusted input drive json-ptr set operations with force enabled, an attacker may alter inherited object properties, creating confidentiality, integrity, or availability impact depending on how the application uses polluted objects.

Executive priority

Treat this as a priority dependency-risk review where json-ptr is used in request handling, configuration parsing, or data transformation. Urgency is lower where the package is unused, unreachable, or only handles trusted static data.

Technical view

The issue is in json-ptr's set operation when the force flag is true. Recursive property creation does not properly reject dangerous keys, enabling prototype pollution. The CVSS 3.1 vector is 7.3 high, network reachable, low complexity, no privileges, and no user interaction, with low impact to confidentiality, integrity, and availability.

Likely exposure

Exposure is most likely in JavaScript or bundled WebJars applications that depend on json-ptr and pass attacker-controlled pointers or object paths into set operations with force=true. Dependency presence alone is not enough to prove reachability.

Exploitation context

The bundle does not show CISA KEV listing or cited active exploitation. The CVSS temporal vector indicates proof-of-concept maturity, but the provided sources do not include exploit details or real-world exploitation evidence.

Researcher notes

Focus validation on reachability, not only package presence. The key condition is unsafe recursive set behavior with force enabled and insufficient key filtering. The provided bundle does not name a specific fixed version, so remediation should be tied to vendor advisory confirmation.

Mitigation direction

  • Inventory direct and transitive json-ptr usage in applications.
  • Check vendor or package guidance for fixed versions before upgrading.
  • Avoid force=true with untrusted pointer input.
  • Reject prototype-related keys before object mutation.
  • Add dependency scanning gates for vulnerable json-ptr versions.

Validation and detection

  • Search code for json-ptr set calls using force=true.
  • Trace whether pointer input can originate from users or external data.
  • Confirm installed json-ptr versions through lockfiles or SBOMs.
  • Run safe regression tests for prototype pollution behavior.
  • Review WebJars npm packaging if Java assets include json-ptr.
Prepared
Confidence
medium
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-7766 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
High
CVSS
7.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/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
7.3CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RL:O/RC:C3.93.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.3High
CVSS 3.1 vector shape for CVE-2020-7766Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/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/ajson-ptr0Listed
Weakness

CWE details

No CWE listed

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