MongoDB Java driver client-side field level encryption not verifying KMS host 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.11.3, 3.12.8, 4.0.6, 4.1.2, 4.2.1
- 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
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Specific versions of the Java driver that support client-side field level encryption (CSFLE) fail to perform correct host name verification on the KMS server’s certificate. This vulnerability in combination with a privileged network position active MITM attack could result in interception of traffic between the Java driver and the KMS service rendering Field Level Encryption ineffective. This issue was discovered during internal testing and affects all versions of the Java driver that support CSFLE. The Java async, Scala, and reactive streams drivers are not impacted. This vulnerability does not impact driver traffic payloads with CSFLE-supported key services originating from applications residing inside the AWS, GCP, and Azure network fabrics due to compensating controls in these environments. This issue does not impact driver workloads that don’t use Field Level Encryption.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- MongoDB Inc. mongo-java-driver
From 3.11 · through 3.11.2; From 3.12 · through 3.12.7
- MongoDB Inc. mongodb-driver
From 3.11 · through 3.11.2; From 3.12 · through 3.12.7
- MongoDB Inc. mongodb-driver-sync
From 3.11 · through 3.11.2; From 3.12 · through 3.12.7; From 4.0 · through 4.0.5; From 4.1 · through 4.1.1
- MongoDB Inc. mongodb-driver-legacy
From 3.11 · through 3.11.2; From 3.12 · through 3.12.7; From 4.0 · through 4.0.5; From 4.1 · through 4.1.1
- org.mongodb:mongodb-driverMaven
From 3.11.0 · fixed in 3.11.3
- org.mongodb:mongodb-driverMaven
From 3.12.0 · fixed in 3.12.8
- org.mongodb:mongodb-driver-syncMaven
From 4.0.0 · fixed in 4.0.6
- org.mongodb:mongodb-driver-syncMaven
From 4.1.0 · fixed in 4.1.2
- org.mongodb:mongodb-driver-syncMaven
From 4.2.0 · fixed in 4.2.1
- org.mongodb:mongo-java-driverMaven
From 3.11.0 · fixed in 3.11.3
- org.mongodb:mongo-java-driverMaven
From 3.12.0 · fixed in 3.12.8
- org.mongodb:mongodb-driver-legacyMaven
From 4.0.0 · fixed in 4.0.6
- org.mongodb:mongodb-driver-legacyMaven
From 4.1.0 · fixed in 4.1.2
- org.mongodb:mongodb-driver-legacyMaven
From 3.11.0 · fixed in 3.11.3
- org.mongodb:mongodb-driver-legacyMaven
From 3.12.0 · fixed in 3.12.8
- org.mongodb:mongodb-driver-syncMaven
From 3.12.0 · fixed in 3.12.8
- org.mongodb:mongodb-driver-syncMaven
From 3.11.0 · fixed in 3.11.3
- org.mongodb:mongodb-driver-legacyMaven
From 4.2.0 · fixed in 4.2.1