GHSA-8332-j7wj-wjw4: Mongoose walks into inherited properties when hydrating, setting, and merging, allowing overwrites of built-in functions (denial of service) and shared schema state
Mongoose is a MongoDB object modeling tool designed to work in an asynchronous environment. Prior to 6.13.12, 7.8.13, 8.24.7, and 9.11.4, Mongoose can descend into inherited properties while loading database documents in init(), setting dotted paths in $set, and merging update documents in utils.mergeClone. Attacker-controlled keys such as toString or valueOf can therefore cause Mongoose to write into shared built-in functions instead of an own property. A crafted document, Mixed path, non-strict document or subdocument, findOneAndReplace() replacement, chained update, or Query.prototype.merge() source can overwrite Object.prototype.toString.call, causing later queries on unrelated models to fail until the process restarts. Separately, when an attacker controls the dotted path passed to doc.set(path, value) for a subdocument configured with strict: false, descent through $set can reach $schema and alter shared validators or schema options for later documents. Mongoose already blocks proto, constructor, and prototype, so this issue overwrites properties on reachable shared objects rather than adding new properties directly to Object.prototype. This issue is fixed in versions 6.13.12, 7.8.13, 8.24.7, and 9.11.4.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
mongooseto a version that resolves this vulnerability.Fixed in 6.13.12 - Upgrade
Upgrade
mongooseto a version that resolves this vulnerability.Fixed in 7.8.13 - Upgrade
Upgrade
mongooseto a version that resolves this vulnerability.Fixed in 8.24.7 - Upgrade
Upgrade
mongooseto a version that resolves this vulnerability.Fixed in 9.11.4
Event History
Frequently Asked Questions
Which Mongoose releases are affected?
The issue affects Mongoose releases before 6.13.12, 7.8.13, 8.24.7, and 9.11.4.
What attacker-controlled input is needed to trigger the denial of service?
An attacker needs influence over keys or dotted paths processed by Mongoose, such as document data containing toString or valueOf, replacement documents for findOneAndReplace(), chained updates, or a source passed to Query.prototype.merge(). Successful overwriting of Object.prototype.toString.call can cause subsequent queries on unrelated models to fail until the process restarts.
When can shared schema state be modified?
Shared schema validators or options can be altered when an attacker controls the dotted path supplied to doc.set(path, value) on a subdocument configured with strict: false. The path can traverse through $__set to $__schema, affecting later documents.
Does this allow direct prototype pollution through __proto__ or constructor?
No. Mongoose already blocks __proto__, constructor, and prototype; the issue instead permits overwriting properties on reachable shared objects, including built-in functions and shared schema state.