Property injection via unsafe recursive merge
Published Feb 18, 2022 · Updated Sep 17, 2024
Prototype pollution in object-extend 0.5.0 and earlier allows remote authenticated users to inject inherited properties via crafted merge input. The recursive merge routine follows an attacker-controlled proto property and copies its nested properties onto Object.prototype. Exploitation requires a consuming application to pass attacker-controlled objects to the library; the demonstrated result is process-wide property injection, while further effects depend on application gadgets.
Summary
What happened
Prototype pollution in object-extend 0.5.0 and earlier allows remote authenticated users to inject inherited properties via crafted merge input. The recursive merge routine follows an attacker-controlled proto property and copies its nested properties onto Object.prototype. Exploitation requires a consuming application to pass attacker-controlled objects to the library; the demonstrated result is process-wide property injection, while further effects depend on application gadgets.
The record
- CVE
- CVE-2021-23702
- Published
- Feb 18, 2022
- Updated
- Sep 17, 2024
- Vendor
- Bernhard Wanger
- Product
- object-extend
- Classifications
- CWE-1321
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 18, 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=0.0.0 <unspecified
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 object-extend 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