Crash via out-of-bounds read in read_pointer
Published Dec 14, 2022 · Updated Apr 22, 2025
Heap-based buffer overflow in Binbloom 2.0 allows local users to crash the program by processing a crafted firmware file. The read_pointer function performs a four-byte read that crosses the end of the heap allocation while compute_candidates processes file data. Exploitation requires a user to run Binbloom on attacker-controlled input; the demonstrated consequence is process termination.
Summary
What happened
Heap-based buffer overflow in Binbloom 2.0 allows local users to crash the program by processing a crafted firmware file. The read_pointer function performs a four-byte read that crosses the end of the heap allocation while compute_candidates processes file data. Exploitation requires a user to run Binbloom on attacker-controlled input; the demonstrated consequence is process termination.
The record
- CVE
- CVE-2022-44910
- Published
- Dec 14, 2022
- Updated
- Apr 22, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-122, CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 14, 2022CVE publishedPublication date reported by the CVE source.
- Apr 22, 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?
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
- Binbloom read_pointer proof of conceptproof of concept · demonstrated
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