Prototype pollution via unsafe JSON Pointer traversal
Published Dec 15, 2022 · Updated Aug 3, 2024
Prototype pollution in Christopher Brown's rfc6902 before 5.0.0 allows context-dependent attackers to modify Object.prototype via crafted patch paths. Pointer.get in pointer.ts traverses each decoded token and previously looked up proto, constructor, and prototype on the current object instead of rejecting or skipping those keys. A consuming application must pass an attacker-controlled path to applyPatch; polluted inherited properties can then alter application behavior, while downstream impact depends on application use.
Summary
What happened
Prototype pollution in Christopher Brown's rfc6902 before 5.0.0 allows context-dependent attackers to modify Object.prototype via crafted patch paths. Pointer.get in pointer.ts traverses each decoded token and previously looked up proto, constructor, and prototype on the current object instead of rejecting or skipping those keys. A consuming application must pass an attacker-controlled path to applyPatch; polluted inherited properties can then alter application behavior, while downstream impact depends on application use.
The record
- CVE
- CVE-2021-4245
- Published
- Dec 15, 2022
- Updated
- Aug 3, 2024
- Vendor
- Christopher Brown
- Product
- rfc6902
- Classifications
- CWE-74, CWE-1321
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 15, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=n/a
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
- applyPatch prototype pollution proof of conceptproof 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