Prototype pollution via non-string path coercion
Published Feb 4, 2022 · Updated Sep 17, 2024
Prototype pollution in skratchdot object-path-set before 1.0.2 allows remote attackers to modify shared object prototypes through setPath. setPath compares each path segment with forbidden string keys, but property access coerces an array-wrapped proto segment after validation and bypasses the check. A consuming application must pass an attacker-controlled path to expose the flaw; the demonstrated result adds an inherited property to subsequently created objects.
Summary
What happened
Prototype pollution in skratchdot object-path-set before 1.0.2 allows remote attackers to modify shared object prototypes through setPath. setPath compares each path segment with forbidden string keys, but property access coerces an array-wrapped proto segment after validation and bypasses the check. A consuming application must pass an attacker-controlled path to expose the flaw; the demonstrated result adds an inherited property to subsequently created objects.
The record
- CVE
- CVE-2021-23507
- Published
- Feb 4, 2022
- Updated
- Sep 17, 2024
- Vendor
- skratchdot
- Product
- object-path-set
- Classifications
- CWE-1321, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 4, 2022CVE publishedPublication date reported by the CVE source.
- Sep 17, 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 <1.0.2
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
- Array-wrapped __proto__ setPath 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