Prototype pollution via array-typed path components
Published Aug 27, 2021 · Updated Sep 16, 2024
Prototype pollution in object-path before 0.11.6 allows attackers to modify inherited object properties via array path components. The set() path walker compares each currentPath directly with proto; an array containing that string fails strict equality and reaches inherited properties. Exploitation requires consuming code to use inherited-properties mode and pass attacker-controlled, non-string path components, enabling changes to Object.prototype that can corrupt application state.
Summary
What happened
Prototype pollution in object-path before 0.11.6 allows attackers to modify inherited object properties via array path components. The set() path walker compares each currentPath directly with proto; an array containing that string fails strict equality and reaches inherited properties. Exploitation requires consuming code to use inherited-properties mode and pass attacker-controlled, non-string path components, enabling changes to Object.prototype that can corrupt application state.
The record
- CVE
- CVE-2021-23434
- Published
- Aug 27, 2021
- Updated
- Sep 16, 2024
- Vendor
- Mario Casciaro
- Product
- object-path
- Classifications
- CWE-843
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 27, 2021CVE 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 <0.11.6
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
- Upstream array-path prototype-pollution regression testproof 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