Crash via out-of-bounds heap access in flushBits
Published Oct 31, 2022 · Updated May 6, 2025
Heap overflow in BitStreamWriter::flushBits() in tsMuxer 2.6.16 allows local users to crash the process via a crafted HEVC stream. During HEVC stream detection, flushBits() reads a four-byte value beyond the end of a heap allocation while updating stream frame-rate bits. A user must open or process the supplied media file, after which the out-of-bounds access terminates tsMuxer without reported data disclosure or modification.
Summary
What happened
Heap overflow in BitStreamWriter::flushBits() in tsMuxer 2.6.16 allows local users to crash the process via a crafted HEVC stream. During HEVC stream detection, flushBits() reads a four-byte value beyond the end of a heap allocation while updating stream frame-rate bits. A user must open or process the supplied media file, after which the out-of-bounds access terminates tsMuxer without reported data disclosure or modification.
The record
- CVE
- CVE-2022-43152
- Published
- Oct 31, 2022
- Updated
- May 6, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499.004, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 31, 2022CVE publishedPublication date reported by the CVE source.
- May 6, 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
- Heap-overflow media-file reproducerproof 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