Prototype pollution via ordinary __proto__ assignment
Published Mar 31, 2022 · Updated Apr 23, 2025
Prototype pollution in deepmerge-ts before 4.0.2 allows attackers to alter object inheritance through crafted merge input. defaultMergeRecords() in src/deepmerge.ts assigns an attacker-controlled proto key with ordinary property assignment, invoking the inherited setter instead of creating an own data property. Exploitation requires an application to pass attacker-controlled objects into the merge API; polluted prototypes can change properties consumed by that application.
Summary
What happened
Prototype pollution in deepmerge-ts before 4.0.2 allows attackers to alter object inheritance through crafted merge input. defaultMergeRecords() in src/deepmerge.ts assigns an attacker-controlled proto key with ordinary property assignment, invoking the inherited setter instead of creating an own data property. Exploitation requires an application to pass attacker-controlled objects into the merge API; polluted prototypes can change properties consumed by that application.
The record
- CVE
- CVE-2022-24802
- Published
- Mar 31, 2022
- Updated
- Apr 23, 2025
- Vendor
- Rebecca Stevens
- Product
- deepmerge-ts
- Classifications
- CWE-915, CWE-1321
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 31, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record 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=< 4.0.2
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
No public exploit references are available in this record.
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