Object prototype modification via unchecked merge keys
Published Sep 10, 2021 · Updated Aug 3, 2024
Prototype pollution in @viking04/merge before 1.0.2 allows context-dependent attackers to modify Object.prototype via crafted merge input. The merge function recursively processes enumerable source keys without rejecting proto or constructor, allowing a crafted source object to write inherited properties. Exploitation requires a consuming application to pass attacker-controlled objects to merge, and the resulting consequence depends on prototype gadgets in that application.
Summary
What happened
Prototype pollution in @viking04/merge before 1.0.2 allows context-dependent attackers to modify Object.prototype via crafted merge input. The merge function recursively processes enumerable source keys without rejecting proto or constructor, allowing a crafted source object to write inherited properties. Exploitation requires a consuming application to pass attacker-controlled objects to merge, and the resulting consequence depends on prototype gadgets in that application.
The record
- CVE
- CVE-2021-3645
- Published
- Sep 10, 2021
- Updated
- Aug 3, 2024
- Vendor
- Viking04
- Product
- @viking04/merge
- Classifications
- CWE-1321
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 10, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=unspecified <1.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
- Upstream prototype-pollution regression payloadproof 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