Authentication bypass via issuer-and-serial-only certificate equality in shared cluster cache
- 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 is affected when applications create clients from certificates supplied by different users and share cached connections. An attacker who supplies a certificate with another user's issuer and serial number can run database operations under that user's identity, exposing or altering the data that identity can access.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
The MongoDB C# Driver compares TLS client certificates by issuer and serial number only when deciding whether two clients can share cached connections. In an application that creates clients from certificates supplied by different users, a user who provides a certificate copying another user's issuer and serial number, without that user's private key, can be given connections authenticated with the other user's certificate. Database operations can then run under the other user's identity, affecting the confidentiality and integrity of data that identity can access.
Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
- MongoDB C# Driver
From 1.8.0 · fixed in 3.13.0