Mongoose prototype pollution in nested virtual paths
Automattic mongoose
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| mongoose npm |
|
|
Automattic mongoose
| Product | Affected | Fixed in |
|---|---|---|
| mongoose npm |
|
|
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, Schema.prototype.virtual() builds nested virtual paths without applying the special-property validation already used by Schema.path() and Schema.add(). An attacker who can influence virtual field names in dynamic schemas, content-management form builders, or schema-as-code systems can supply path segments such as __proto__, constructor, or prototype, causing the virtual-path reducer to write enumerable properties to Object.prototype or Function.prototype. The resulting prototype pollution can spoof inherited property checks such as authorization flags and can provide function-prototype gadget state to other server-side JavaScript code. This issue is fixed in versions 6.13.12, 7.8.13, 8.24.7, and 9.11.4.
From the CVE record · GitHub_M
Mongoose's Schema.prototype.virtual() does not validate special property names when building nested virtual paths. An attacker who can influence virtual field names in dynamic schemas can pollute Object.prototype or Function.prototype, potentially spoofing inherited authorization flags or affecting other server-side JavaScript code. The input does not establish whether network access, authentication, or user interaction is required.
Check applications using npm mongoose versions before 6.13.12, 7.0.0 through before 7.8.13, 8.0.0 through before 8.24.7, or 9.0.0 through before 9.11.4.