Plaintext exposure of encrypted fields via ANSI code-page corruption of database name
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| MongoDB | C# Driver | unaffected |
|
||||||
| MongoDB | MongoDB.Libmongocrypt NuGet package | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Mongodb | C# Driver |
|
||||||||
| Mongodb | Mongodb.libmongocrypt Nuget Package |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.108% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Mongodb
Mongodb c# Driver Mongodb mongodb.libmongocrypt Nuget Package |
|
| Vendors & Products |
Mongodb
Mongodb c# Driver Mongodb mongodb.libmongocrypt Nuget Package |
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Plaintext exposure of encrypted fields via ANSI code-page corruption of database name | |
| Weaknesses | CWE-838 | |
| References |
| |
| Metrics |
cvssV3_1
|