Application crash via AUPR header size overflow
Published Mar 1, 2022 · Updated Aug 4, 2024
Integer overflow in DTSStreamReader in tsMuxer Project tsMuxer git-2678966 allows local users to crash it via a crafted DTS file. The findFrame() bounds check adds an attacker-controlled AUPR header size to the buffer pointer, allowing pointer wraparound to make an undersized buffer appear valid. Exploitation requires a user to process the file locally and interrupts only that tsMuxer process, with no reported data disclosure or modification.
Summary
What happened
Integer overflow in DTSStreamReader in tsMuxer Project tsMuxer git-2678966 allows local users to crash it via a crafted DTS file. The findFrame() bounds check adds an attacker-controlled AUPR header size to the buffer pointer, allowing pointer wraparound to make an undersized buffer appear valid. Exploitation requires a user to process the file locally and interrupts only that tsMuxer process, with no reported data disclosure or modification.
The record
- CVE
- CVE-2021-45860
- Published
- Mar 1, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-190, 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.
Weakness, pattern, technique
Public exploit references
- Crafted DTS 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