Process crash via __proto__ dictionary-key pollution
Published Feb 17, 2022 · Updated Aug 3, 2024
Prototype pollution in plist before 3.0.5 allows attackers to alter inherited object properties through crafted XML input. The parsePlistXML routine accepts proto as a dictionary key and assigns the nested dictionary to a plain JavaScript object, modifying its prototype. Any application that passes attacker-controlled XML to parse() is exposed; property corruption permits a process crash, while code execution requires a suitable downstream gadget.
Summary
What happened
Prototype pollution in plist before 3.0.5 allows attackers to alter inherited object properties through crafted XML input. The parsePlistXML routine accepts proto as a dictionary key and assigns the nested dictionary to a plain JavaScript object, modifying its prototype. Any application that passes attacker-controlled XML to parse() is exposed; property corruption permits a process crash, while code execution requires a suitable downstream gadget.
The record
- CVE
- CVE-2022-22912
- Published
- Feb 17, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-1321
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 17, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Crafted __proto__ XML 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