Prototype pollution via unsanitized dotted argument keys
Published Mar 16, 2020 · Updated Aug 4, 2024
Prototype pollution in affected yargs-parser releases allows attackers controlling parsed arguments to modify Object.prototype properties. The parser expands dotted option keys into nested objects without sanitizing proto, so assignment traverses and writes the shared object prototype. Exploitation requires an application to pass attacker-controlled arguments; polluted properties can alter every ordinary object in that process.
Summary
What happened
Prototype pollution in affected yargs-parser releases allows attackers controlling parsed arguments to modify Object.prototype properties. The parser expands dotted option keys into nested objects without sanitizing proto, so assignment traverses and writes the shared object prototype. Exploitation requires an application to pass attacker-controlled arguments; polluted properties can alter every ordinary object in that process.
The record
- CVE
- CVE-2020-7608
- Published
- Mar 16, 2020
- Updated
- Aug 4, 2024
- Vendor
- yargs
- Product
- yargs-parser
- Classifications
- CWE-1321, CWE-915
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Mar 16, 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 18.1.1 and patches at 13.1.2 and 15.0.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
- GitHub advisory prototype-pollution demonstrationproof 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