Automattic Mongoose
Mongoose: Connection-level sanitizeFilter not applied
Mongoose is a MongoDB object modeling tool designed to work in an asynchronous environment. From 6.0.0 until 6.13.12, 7.8.13, 8.24.7, and 9.11.4, Mongoose stores the connection-level sanitizeFilter option in Connection.config, but Query.prototype._castConditions() and query casting check other option locations and do not read that configuration. An application that enables sanitizeFilter through mongoose.connect() or createConnection() and passes an attacker-controlled object into a query filter therefore receives a connection that reports the defense as enabled while query selector objects remain unsanitized. A crafted password value using a query operator can match an account record without the expected literal password, while global configuration through mongoose.set('sanitizeFilter') and per-query Model.find().sanitizeFilter() remain unaffected. This issue is fixed in versions 6.13.12, 7.8.13, 8.24.7, and 9.11.4.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 6.0.0, < 6.13.12
- >= 7.0.0, < 7.8.13
- >= 8.0.0, < 8.24.7
- >= 9.0.0, < 9.11.4
Fixed in 6.13.12, 7.8.13, 8.24.7, 9.11.4
Mitigation
Upgrade mongoose to 6.13.12 or 7.8.13 or 8.24.7 or 9.11.4 or later.
References
- Vendor advisory github.com/Automattic/mongoose/security/adviso…
- Patch github.com/Automattic/mongoose/commit/4bb65947…
- Patch github.com/Automattic/mongoose/commit/4f4f9a79…
5 more
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.