Process crash via unchecked buffer-length addition
Published Jan 12, 2024 · Updated Nov 4, 2025
Integer overflow in libebml before 1.4.5 allows remote attackers to crash a consuming process through input requiring user interaction. MemIOCallback read and write paths add the current buffer position to a caller-supplied byte count without first checking whether the unsigned sum wraps. A wrapped sum bypasses bounds handling and can trigger an out-of-bounds copy and segmentation fault; no code execution has been demonstrated.
Summary
What happened
Integer overflow in libebml before 1.4.5 allows remote attackers to crash a consuming process through input requiring user interaction. MemIOCallback read and write paths add the current buffer position to a caller-supplied byte count without first checking whether the unsigned sum wraps. A wrapped sum bypasses bounds handling and can trigger an out-of-bounds copy and segmentation fault; no code execution has been demonstrated.
The record
- CVE
- CVE-2023-52339
- Published
- Jan 12, 2024
- Updated
- Nov 4, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-190, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 12, 2024CVE publishedPublication date reported by the CVE source.
- Nov 4, 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.
Public exploit references
- MemIOCallback read integer-overflow 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