Application state corruption via unfiltered recursive merge
Published May 1, 2022 · Updated Sep 17, 2024
Prototype pollution in dset before 3.1.2 allows remote attackers to modify Object.prototype through crafted dset/merge input. The path guard checks only top-level segments, while the merge helper recursively copies nested object keys without rejecting prototype-sensitive names. Exploitation requires consuming code to pass an attacker-controlled object to dset/merge; inherited properties can then corrupt application state.
Summary
What happened
Prototype pollution in dset before 3.1.2 allows remote attackers to modify Object.prototype through crafted dset/merge input. The path guard checks only top-level segments, while the merge helper recursively copies nested object keys without rejecting prototype-sensitive names. Exploitation requires consuming code to pass an attacker-controlled object to dset/merge; inherited properties can then corrupt application state.
The record
- CVE
- CVE-2022-25645
- Published
- May 1, 2022
- Updated
- Sep 17, 2024
- Vendor
- Luke Edwards
- Product
- dset
- Classifications
- CWE-1321
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 1, 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 <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 dset/merge 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