Prototype pollution via array pointer tokens
Published Dec 26, 2022 · Updated Aug 3, 2024
Prototype pollution in json-pointer 0.6.0 and 0.6.1 allows remote attackers to alter object prototypes via crafted pointer tokens. The index.js set function accepts array-valued pointer components, converts them into property names, and can reach proto, constructor, or prototype assignments without adequate filtering. Exploitation requires an application to pass attacker-controlled pointer data to set; resulting prototype changes can affect confidentiality, integrity, and availability of that Node.js process.
Summary
What happened
Prototype pollution in json-pointer 0.6.0 and 0.6.1 allows remote attackers to alter object prototypes via crafted pointer tokens. The index.js set function accepts array-valued pointer components, converts them into property names, and can reach proto, constructor, or prototype assignments without adequate filtering. Exploitation requires an application to pass attacker-controlled pointer data to set; resulting prototype changes can affect confidentiality, integrity, and availability of that Node.js process.
The record
- CVE
- CVE-2022-4742
- Published
- Dec 26, 2022
- Updated
- Aug 3, 2024
- Vendor
- Manuel Stofer
- Product
- json-pointer
- Classifications
- CWE-1321
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 26, 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=0.6.0
- Affected versionversion=0.6.1
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
No public exploit references are available in this record.
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