GHSA-jvpx-6w8x-h6rg: Plaintext exposure of encrypted fields via ANSI code-page corruption of database name
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.
Affected Software
Event History
Frequently Asked Questions
Which deployments are exposed to this issue?
Exposure is limited to applications using the MongoDB .NET/C# driver's client-side field-level encryption support where the relevant platform text-encoding configuration triggers the internal name-conversion information loss. The affected operation must also have encryption rules configured for the fields involved.
What does an attacker need to do to exploit the flaw?
The attacker needs the ability to write data through an affected application. They can cause data intended for client-side field-level encryption to be persisted without encryption when the encoding condition is present.
Will the application report a failed encryption operation?
No. The encryption layer can fail to associate the operation with its configured encryption rules and allows the operation to proceed without raising an error.
What is the security impact if exploitation succeeds?
Sensitive fields can be stored in plaintext, defeating the confidentiality protection expected from client-side field-level encryption. No integrity or availability impact was observed.