Heap corruption via undersized string buffer allocation
Published Jul 3, 2024 · Updated Nov 3, 2025
Heap-based buffer overflow in MongoDB libbson before 1.27.1 allows remote attackers to corrupt heap memory through appended strings. bson_string_append computes an insufficient destination allocation for some input lengths, then writes beyond it into adjacent heap storage. Network reachability depends on a consuming application passing attacker-controlled strings to this library function; the published impact is adjacent heap corruption.
Summary
What happened
Heap-based buffer overflow in MongoDB libbson before 1.27.1 allows remote attackers to corrupt heap memory through appended strings. bson_string_append computes an insufficient destination allocation for some input lengths, then writes beyond it into adjacent heap storage. Network reachability depends on a consuming application passing attacker-controlled strings to this library function; the published impact is adjacent heap corruption.
The record
- CVE
- CVE-2024-6383
- Published
- Jul 3, 2024
- Updated
- Nov 3, 2025
- Vendor
- MongoDB
- Product
- libbson
- Classifications
- CWE-122
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 3, 2024CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.27.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo