Prototype pollution via unsafe XML key handling
Published Mar 22, 2022 · Updated Aug 3, 2024
Prototype pollution in simple-plist 1.3.0 allows remote attackers to alter parsed object properties via crafted XML plist input. The parse() function accepts an XML proto key and assigns nested properties such as length onto the returned object prototype. Exploitation requires a consumer to parse attacker-controlled XML; polluted properties alter application logic, with impact depending on consuming code.
Summary
What happened
Prototype pollution in simple-plist 1.3.0 allows remote attackers to alter parsed object properties via crafted XML plist input. The parse() function accepts an XML proto key and assigns nested properties such as length onto the returned object prototype. Exploitation requires a consumer to parse attacker-controlled XML; polluted properties alter application logic, with impact depending on consuming code.
The record
- CVE
- CVE-2022-26260
- Published
- Mar 22, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-1321
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 22, 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.
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
- XML __proto__ 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