Inherited property modification via recursive merge
Published Jul 25, 2022 · Updated Sep 16, 2024
Prototype pollution in Ian Walter @ianwalter/merge 9.0.1 and earlier allows remote attackers to modify inherited object properties. The main merge function recursively follows an attacker-supplied proto key into Object.prototype and copies nested properties there. Reachability requires a consuming application to pass an attacker-controlled object to merge, and the resulting consequence depends on how that application uses polluted properties.
Summary
What happened
Prototype pollution in Ian Walter @ianwalter/merge 9.0.1 and earlier allows remote attackers to modify inherited object properties. The main merge function recursively follows an attacker-supplied proto key into Object.prototype and copies nested properties there. Reachability requires a consuming application to pass an attacker-controlled object to merge, and the resulting consequence depends on how that application uses polluted properties.
The record
- CVE
- CVE-2021-23397
- Published
- Jul 25, 2022
- Updated
- Sep 16, 2024
- Vendor
- Ian Walter
- Product
- @ianwalter/merge
- Classifications
- CWE-1321
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 25, 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=0 <unspecified
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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 __proto__ merge proof of conceptproof of concept · unverified
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