Crash via unchecked negative MOV track identifier
Published Nov 14, 2024 · Updated Nov 20, 2024
Heap-based buffer under-read in tsMuxer nightly-2024-05-12-02-01-18 allows attackers to crash the application via a crafted MOV file. MovDemuxer::mov_read_trun accepts a negative track_id and indexes backward from the tracks array, triggering an invalid read and segmentation fault. Exploitation requires a user to open or process the file and interrupts only that tsMuxer process.
Summary
What happened
Heap-based buffer under-read in tsMuxer nightly-2024-05-12-02-01-18 allows attackers to crash the application via a crafted MOV file. MovDemuxer::mov_read_trun accepts a negative track_id and indexes backward from the tracks array, triggering an invalid read and segmentation fault. Exploitation requires a user to open or process the file and interrupts only that tsMuxer process.
The record
- CVE
- CVE-2024-52613
- Published
- Nov 14, 2024
- Updated
- Nov 20, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 14, 2024CVE publishedPublication date reported by the CVE source.
- Nov 20, 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
- 15-b.mov 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