NoSQL injection via mismatched BSON size prefix in raw document splice to the wire protocol
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.14.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The MongoDB Java Driver, which applications use to talk to MongoDB databases, is affected. A flaw in how it handles raw document data can let an attacker who can influence that data change the database commands the application actually runs, potentially reading or modifying data under the application's permissions.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
A BSON encoding component of the MongoDB Java Driver does not verify that an externally supplied raw document's self-declared length agrees with the extent of the byte range it is given before that range is copied into an outgoing database command. An application that wraps untrusted raw bytes in such a document and uses it as part of a command can therefore emit a structurally inconsistent message, causing the database to interpret attacker-supplied trailing content as additional fields of the surrounding command. No authentication to the driver or database is required beyond the ability to influence those bytes through the victim application, and no user interaction is needed. The result is unintended modification of the command actually executed, which can alter the data read or written under the application's credentials.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- MongoDB Java Driver
From 5.8.0 · fixed in 5.14.0