Prototype pollution via array pointer type confusion
Published Nov 3, 2021 · Updated Sep 16, 2024
Prototype pollution in Jan Lehnardt jsonpointer before 5.0.0 allows attackers to modify inherited properties via crafted pointer arrays. The setter compares array-valued path components directly with reserved strings, so JavaScript coerces them to dangerous property keys only after the strict-equality guard is bypassed. Reachability requires consuming code to pass attacker-controlled pointer components to the set operation; polluted properties can alter application behavior and data handling.
Summary
What happened
Prototype pollution in Jan Lehnardt jsonpointer before 5.0.0 allows attackers to modify inherited properties via crafted pointer arrays. The setter compares array-valued path components directly with reserved strings, so JavaScript coerces them to dangerous property keys only after the strict-equality guard is bypassed. Reachability requires consuming code to pass attacker-controlled pointer components to the set operation; polluted properties can alter application behavior and data handling.
The record
- CVE
- CVE-2021-23807
- Published
- Nov 3, 2021
- Updated
- Sep 16, 2024
- Vendor
- Jan Lehnardt
- Product
- jsonpointer
- Classifications
- CWE-843
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Nov 3, 2021CVE publishedPublication date reported by the CVE source.
- Sep 16, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <5.0.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream array-pointer prototype-pollution payloadsproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo