Prototype pollution via unchecked recursive object merge
Published Jun 19, 2020 · Updated Sep 16, 2024
Prototype pollution in all CasperJS versions allows remote attackers to modify Object.prototype through crafted merge input. The mergeObjects utility recursively enumerates source keys and assigns them into the destination without rejecting proto, so a crafted object writes inherited properties globally. Reachability requires consuming code to pass attacker-controlled objects into mergeObjects; the resulting effect depends on how downstream logic uses polluted properties.
Summary
What happened
Prototype pollution in all CasperJS versions allows remote attackers to modify Object.prototype through crafted merge input. The mergeObjects utility recursively enumerates source keys and assigns them into the destination without rejecting proto, so a crafted object writes inherited properties globally. Reachability requires consuming code to pass attacker-controlled objects into mergeObjects; the resulting effect depends on how downstream logic uses polluted properties.
The record
- CVE
- CVE-2020-7679
- Published
- Jun 19, 2020
- Updated
- Sep 16, 2024
- Vendor
- CasperJS
- Product
- CasperJS
- Classifications
- CWE-915, CWE-1321
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 19, 2020CVE 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
- GitHub Advisory Database 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