Crash via unchecked HEVC frame-rate bit offset
Published Mar 1, 2022 · Updated Aug 4, 2024
Heap-based buffer overflow in tsMuxer git-2678966 allows local users to crash the application by opening a crafted HEVC file. HevcUnit::updateBits reads beyond its heap allocation while rewriting frame-rate bits because the requested bit offset is not checked against the decoded buffer. Exploitation requires a user to process the file; the demonstrated consequence is an application abort and service interruption, with no published data impact.
Summary
What happened
Heap-based buffer overflow in tsMuxer git-2678966 allows local users to crash the application by opening a crafted HEVC file. HevcUnit::updateBits reads beyond its heap allocation while rewriting frame-rate bits because the requested bit offset is not checked against the decoded buffer. Exploitation requires a user to process the file; the demonstrated consequence is an application abort and service interruption, with no published data impact.
The record
- CVE
- CVE-2021-45863
- Published
- Mar 1, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 1, 2022CVE 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
- HevcUnit::updateBits proof-of-concept fileproof 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