Application crash via zero MLP sample rate
Published Jun 23, 2021 · Updated Aug 4, 2024
Divide by zero in tsMuxer 2.6.16 allows context-dependent attackers to crash the application through a crafted media file. AC3Codec::decodeDtsHdFrame accepts a zero MLP group-one sample rate and later uses that value as a divisor in ac3Codec.cpp. A user must run tsMuxer on the file; processing aborts with a floating-point exception, interrupting only that application instance.
Summary
What happened
Divide by zero in tsMuxer 2.6.16 allows context-dependent attackers to crash the application through a crafted media file. AC3Codec::decodeDtsHdFrame accepts a zero MLP group-one sample rate and later uses that value as a divisor in ac3Codec.cpp. A user must run tsMuxer on the file; processing aborts with a floating-point exception, interrupting only that application instance.
The record
- CVE
- CVE-2021-34069
- Published
- Jun 23, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-369, T1499.004
- 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
- decoder_poc crafted-file sampleproof 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