Prototype pollution via unsafe recursive merge
Published Mar 11, 2020 · Updated Aug 4, 2024
Prototype pollution in XCritical Software utilitify before 1.0.3 allows attackers to modify Object.prototype through crafted merge input. The mergeDeep function recursively copies enumerable keys without excluding proto, constructor, or prototype, allowing those keys to reach prototype objects. Exploitation requires a consuming application to pass attacker-controlled object keys into mergeDeep; polluted inherited properties can then alter application behavior.
Summary
What happened
Prototype pollution in XCritical Software utilitify before 1.0.3 allows attackers to modify Object.prototype through crafted merge input. The mergeDeep function recursively copies enumerable keys without excluding proto, constructor, or prototype, allowing those keys to reach prototype objects. Exploitation requires a consuming application to pass attacker-controlled object keys into mergeDeep; polluted inherited properties can then alter application behavior.
The record
- CVE
- CVE-2019-10808
- Published
- Mar 11, 2020
- Updated
- Aug 4, 2024
- Vendor
- XCritical Software
- Product
- utilitify
- Classifications
- CWE-1321
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Mar 11, 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 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 mergeDeep prototype-pollution regression caseproof 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