BSON output corruption via out-of-range binary subtype bypassing UUID and OldBinary guards
- 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 3.13.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 C# Driver's BSON library is affected, so applications that parse untrusted text into binary values can end up storing malformed BSON data. This can cause later readers to fail with errors or to misinterpret binary fields as shorter than what was originally validated.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
A numeric-type conversion flaw in the BSON handling library of the MongoDB C# Driver allows an out-of-range binary subtype value supplied through untrusted textual input to bypass the library's binary-element integrity checks. When such a value is later encoded, it is narrowed to a smaller wire representation, producing binary elements that misdeclare their type or length. An unauthenticated party able to supply text parsed by an affected application can cause it to emit and persist malformed binary data, which subsequent readers either reject with an error or silently interpret as shorter than the data that was validated.
Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
- MongoDB C# Driver
From 2.0.0 · fixed in 3.13.0