Object prototype pollution via unsafe path traversal
Published Feb 4, 2020 · Updated Aug 4, 2024
Prototype pollution in Sindre Sorhus dot-prop before 4.2.1 and 5.0.0 through 5.1.0 allows attackers to modify shared object properties. The path parser accepts proto, prototype, and constructor segments, so the setter traverses into a shared prototype and assigns the supplied value. Exploitation requires a consuming application to pass an attacker-controlled dot path to the setter; resulting effects depend on how polluted properties are used.
Summary
What happened
Prototype pollution in Sindre Sorhus dot-prop before 4.2.1 and 5.0.0 through 5.1.0 allows attackers to modify shared object properties. The path parser accepts proto, prototype, and constructor segments, so the setter traverses into a shared prototype and assigns the supplied value. Exploitation requires a consuming application to pass an attacker-controlled dot path to the setter; resulting effects depend on how polluted properties are used.
The record
- CVE
- CVE-2020-8116
- Published
- Feb 4, 2020
- Updated
- Aug 4, 2024
- Vendor
- Sindre Sorhus
- Product
- dot-prop
- Classifications
- CWE-1321, CWE-471
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 4, 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=5.x before 5.1.1
- Affected versionversion=before 4.2.1
- Affected versionversion=Fixed in 5.1.1
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
- HackerOne prototype-pollution 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