Heap overflow via oversized decrypted TLS record sequence in Windows Secure Channel stream
- 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
- 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
A heap-based buffer overflow exists in the TLS transport layer of the MongoDB C Driver when built with the Windows platform TLS backend. A remote endpoint that the client connects to can cause the driver to write uncontrolled data outside the bounds of a heap allocation while processing incoming encrypted traffic after the TLS handshake completes. No authentication or user interaction is required, because the affected processing occurs before any application-level authentication completes. Triggering this issue may lead to memory corruption in the client process, disclosure of adjacent heap memory, or termination of the process.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- MongoDB Inc. C Driver
From 2.3.0 · through 2.3.3; From 2.2.0 · through 2.2.4; From 2.1.0 · through 2.1.2; From 2.0.0 · through 2.0.2; From 1.30.0 · through 1.30.8; From 1.29.0 · through 1.29.2; From 1.28.0 · through 1.28.1; From 1.27.0 · through 1.27.6; From 1.26.0 · through 1.26.2; From 1.25.0 · through 1.25.4; From 1.24.0 · through 1.24.4