Plaintext exposure of encrypted fields via ANSI code-page corruption of database name
- 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 .NET/C# driver's client-side field-level encryption feature is affected on systems with certain text-encoding configurations. Sensitive fields that should be encrypted can instead be stored in plaintext in the database, which defeats the confidentiality protection that client-side encryption is meant to provide.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
A flaw in the client-side encryption support of the MongoDB .NET/C# driver can cause data designated for client-side field-level encryption to be written without encryption. Under certain platform text-encoding configurations, an internal name conversion loses information, so the encryption layer fails to associate the operation with its configured encryption rules and the operation proceeds without an error being raised. An application user with the ability to write data through an affected application can therefore have sensitive fields persisted in plaintext, defeating the confidentiality guarantee that client-side encryption is intended to provide. No integrity or availability impact was observed.
Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
- MongoDB C# Driver
From 2.10.0 · fixed in 3.13.0
- MongoDB MongoDB.Libmongocrypt NuGet package
From 1.0.0 · through 1.12.0