Application crash via truncated BSON allocation size
Published Apr 24, 2020 · Updated Aug 4, 2024
Integer overflow in the legacy MongoDB C driver's bson library before 0.8 allows local users to crash BSON-consuming applications. The bson_ensure_space function accepts bytesNeeded as a signed int, so a sufficiently large calculated size wraps before buffer reallocation. Exploitation requires an application to process attacker-controlled BSON; in Whoopsie, crafted crash-report parsing terminates the service.
Summary
What happened
Integer overflow in the legacy MongoDB C driver's bson library before 0.8 allows local users to crash BSON-consuming applications. The bson_ensure_space function accepts bytesNeeded as a signed int, so a sufficiently large calculated size wraps before buffer reallocation. Exploitation requires an application to process attacker-controlled BSON; in Whoopsie, crafted crash-report parsing terminates the service.
The record
- CVE
- CVE-2020-12135
- Published
- Apr 24, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-190, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 24, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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