Prototype pollution via unsafe recursive prototype merge
Published Dec 10, 2021 · Updated Sep 16, 2024
Prototype pollution in Luyuan merge-deep2 allows remote attackers to alter inherited object properties through crafted input to mergeDeep(). When prototype merging is enabled, the function recursively follows an attacker-controlled proto property and copies nested values onto Object.prototype. Exploitation requires a consuming application to pass attacker-controlled objects with the third argument enabled; consequences depend on how inherited properties affect that application.
Summary
What happened
Prototype pollution in Luyuan merge-deep2 allows remote attackers to alter inherited object properties through crafted input to mergeDeep(). When prototype merging is enabled, the function recursively follows an attacker-controlled proto property and copies nested values onto Object.prototype. Exploitation requires a consuming application to pass attacker-controlled objects with the third argument enabled; consequences depend on how inherited properties affect that application.
The record
- CVE
- CVE-2021-23700
- Published
- Dec 10, 2021
- Updated
- Sep 16, 2024
- Vendor
- Luyuan
- Product
- merge-deep2
- Classifications
- CWE-1321
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 10, 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=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 merge-deep2 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