Prototype pollution via constructor.prototype key paths
Published May 13, 2022 · Updated Sep 16, 2024
Prototype pollution in monsterkodi SDS 0.0.0 and later allows attackers to modify Object.prototype via a crafted key path. The set function in js/set.js rejects proto but traverses constructor.prototype and assigns the supplied value to the shared prototype. Reachability depends on a caller passing attacker-controlled paths to set; polluted properties then affect other objects in that Node.js process.
Summary
What happened
Prototype pollution in monsterkodi SDS 0.0.0 and later allows attackers to modify Object.prototype via a crafted key path. The set function in js/set.js rejects proto but traverses constructor.prototype and assigns the supplied value to the shared prototype. Reachability depends on a caller passing attacker-controlled paths to set; polluted properties then affect other objects in that Node.js process.
The record
- CVE
- CVE-2022-25862
- Published
- May 13, 2022
- Updated
- Sep 16, 2024
- Vendor
- monsterkodi
- Product
- SDS
- Classifications
- CWE-1321
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 13, 2022CVE publishedPublication date reported by the CVE source.
- Sep 16, 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.0.0 <unspecified
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
- SDS constructor.prototype proof of conceptproof of concept · unverified
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