Application crash via HEVC heap over-read
Published Jun 23, 2021 · Updated Aug 4, 2024
Heap buffer overflow in tsMuxer 2.6.16 allows local users to crash the application by processing a crafted HEVC file. HEVC frame-rate updating reaches BitStreamWriter::flushBits, which reads four bytes beyond a heap buffer allocated by HevcUnit::decodeBuffer. The crafted file must be processed locally; the published evidence demonstrates an abort and does not establish code execution.
Summary
What happened
Heap buffer overflow in tsMuxer 2.6.16 allows local users to crash the application by processing a crafted HEVC file. HEVC frame-rate updating reaches BitStreamWriter::flushBits, which reads four bytes beyond a heap buffer allocated by HevcUnit::decodeBuffer. The crafted file must be processed locally; the published evidence demonstrates an abort and does not establish code execution.
The record
- CVE
- CVE-2021-34067
- Published
- Jun 23, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 23, 2021CVE 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.
Public exploit references
- crash_2 crafted-file 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