Prototype pollution via unchecked schema paths
Published Jul 28, 2022 · Updated Nov 20, 2024
Prototype pollution in Automattic Mongoose before 6.4.6 allows remote attackers to modify Object.prototype through a crafted schema path. Schema.add and Schema.path split attacker-controlled dotted property names and traverse proto without rejecting the inherited special property, so later assignments reach the global prototype. Exploitation requires an application to pass attacker-controlled schema definitions into Mongoose; polluted properties can corrupt process behavior and cause a service crash.
Summary
What happened
Prototype pollution in Automattic Mongoose before 6.4.6 allows remote attackers to modify Object.prototype through a crafted schema path. Schema.add and Schema.path split attacker-controlled dotted property names and traverse proto without rejecting the inherited special property, so later assignments reach the global prototype. Exploitation requires an application to pass attacker-controlled schema definitions into Mongoose; polluted properties can corrupt process behavior and cause a service crash.
The record
- CVE
- CVE-2022-2564
- Published
- Jul 28, 2022
- Updated
- Nov 20, 2024
- Vendor
- Automattic
- Product
- Mongoose
- Classifications
- CWE-1321, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 28, 2022CVE publishedPublication date reported by the CVE source.
- Nov 20, 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=unspecified <6.4.6
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 __proto__.toString regression payloadproof 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