Process-wide property injection via unsanitized path traversal
Published Jul 17, 2022 · Updated Sep 17, 2024
Prototype pollution in grunt-util-property 0.0.2 and earlier allows attackers to modify Object.prototype through a crafted property path. The call method follows dot-delimited segments without rejecting proto, then assigns the supplied value through that inherited prototype reference. Exploitation requires a consuming application to pass attacker-controlled path data to call; resulting property changes affect every object in that Node.js process.
Summary
What happened
Prototype pollution in grunt-util-property 0.0.2 and earlier allows attackers to modify Object.prototype through a crafted property path. The call method follows dot-delimited segments without rejecting proto, then assigns the supplied value through that inherited prototype reference. Exploitation requires a consuming application to pass attacker-controlled path data to call; resulting property changes affect every object in that Node.js process.
The record
- CVE
- CVE-2020-7641
- Published
- Jul 17, 2022
- Updated
- Sep 17, 2024
- Vendor
- Mikael Karon
- Product
- grunt-util-property
- Classifications
- CWE-1321
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 17, 2022CVE publishedPublication date reported by the CVE source.
- Sep 17, 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?
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
- Snyk grunt-util-property call-method 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