Object prototype modification via unsafe path traversal
Published Apr 6, 2020 · Updated Aug 4, 2024
Prototype pollution in Eivind Fjeldstad @eivifj/dot before 1.0.3 allows attackers to modify Object.prototype via crafted paths. The set function splits a supplied dot path and follows inherited properties without verifying that each segment belongs to the target object, so proto reaches the shared prototype before assignment. Exploitation requires a consuming application to pass an attacker-controlled path to set; polluted properties can alter object behavior throughout that process.
Summary
What happened
Prototype pollution in Eivind Fjeldstad @eivifj/dot before 1.0.3 allows attackers to modify Object.prototype via crafted paths. The set function splits a supplied dot path and follows inherited properties without verifying that each segment belongs to the target object, so proto reaches the shared prototype before assignment. Exploitation requires a consuming application to pass an attacker-controlled path to set; polluted properties can alter object behavior throughout that process.
The record
- CVE
- CVE-2020-7639
- Published
- Apr 6, 2020
- Updated
- Aug 4, 2024
- Vendor
- Eivind Fjeldstad
- Product
- @eivifj/dot
- Classifications
- CWE-1321
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 6, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=All versions below 1.0.3
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
- Upstream prototype-pollution regression testproof 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