Application crash via out-of-bounds VC-1 header read
Published Apr 14, 2021 · Updated Aug 3, 2024
Heap buffer overflow in tsMuxer 2.6.16 allows local users to crash the application by opening a crafted WAV file. During stream detection, BitStreamReader::getCurVal reads one byte beyond a one-byte heap buffer while VC1SequenceHeader::decode_entry_point parses the crafted input. Exploitation requires a local user to run tsMuxer against the file and results in process termination rather than reported data disclosure or modification.
Summary
What happened
Heap buffer overflow in tsMuxer 2.6.16 allows local users to crash the application by opening a crafted WAV file. During stream detection, BitStreamReader::getCurVal reads one byte beyond a one-byte heap buffer while VC1SequenceHeader::decode_entry_point parses the crafted input. Exploitation requires a local user to run tsMuxer against the file and results in process termination rather than reported data disclosure or modification.
The record
- CVE
- CVE-2021-26805
- Published
- Apr 14, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 14, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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
- poc.zip malformed WAV 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