Prototype pollution via unfiltered set path
Published Feb 18, 2020 · Updated Aug 4, 2024
Prototype pollution in Snyk dot-object before 2.1.3 allows attackers to modify Object.prototype through a crafted property path. The set function recursively assigns path segments without rejecting proto, prototype, or constructor keys, so a special segment resolves to Object.prototype instead of an own property. Exploitation requires an application to pass attacker-controlled paths and values to set; successful pollution changes properties inherited by objects in that Node.js process.
Summary
What happened
Prototype pollution in Snyk dot-object before 2.1.3 allows attackers to modify Object.prototype through a crafted property path. The set function recursively assigns path segments without rejecting proto, prototype, or constructor keys, so a special segment resolves to Object.prototype instead of an own property. Exploitation requires an application to pass attacker-controlled paths and values to set; successful pollution changes properties inherited by objects in that Node.js process.
The record
- CVE
- CVE-2019-10793
- Published
- Feb 18, 2020
- Updated
- Aug 4, 2024
- Vendor
- Snyk
- Product
- dot-object
- Classifications
- CWE-1321
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 18, 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 prior to version 2.1.3
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
- JHU System Security Lab dot-object 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