Prototype pollution via unchecked nested path assignment
Published Mar 17, 2022 · Updated Sep 16, 2024
Prototype pollution in ahdinosaur set-in before 2.0.3 allows attackers to modify inherited object properties via crafted path arrays. The setIn recursion assigns object[key] = value after an incomplete guard accepts array-wrapped dangerous keys such as proto. Exploitation requires an embedding application to pass attacker-controlled path arrays; polluted properties then alter downstream data or behavior.
Summary
What happened
Prototype pollution in ahdinosaur set-in before 2.0.3 allows attackers to modify inherited object properties via crafted path arrays. The setIn recursion assigns object[key] = value after an incomplete guard accepts array-wrapped dangerous keys such as proto. Exploitation requires an embedding application to pass attacker-controlled path arrays; polluted properties then alter downstream data or behavior.
The record
- CVE
- CVE-2022-25354
- Published
- Mar 17, 2022
- Updated
- Sep 16, 2024
- Vendor
- ahdinosaur
- Product
- set-in
- Classifications
- CWE-1321
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 17, 2022CVE 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 <2.0.3
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
- Snyk setIn array-wrapped __proto__ 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