Application crash via unsigned loop-bound underflow
Published Feb 18, 2025 · Updated Feb 20, 2025
A NULL pointer dereference in FFmpeg git master before commit fd1772 allows attackers to crash MOV processing via a zero-entry timing table. In mov_read_trak, a zero tts_count makes the unsigned tts_count - 1 loop bound wrap to UINT_MAX, and the loop indexes a NULL tts_data array. Processing a MOV-family file with that empty timing state is required; FFmpeg states that no released version was ever affected.
Summary
What happened
A NULL pointer dereference in FFmpeg git master before commit fd1772 allows attackers to crash MOV processing via a zero-entry timing table. In mov_read_trak, a zero tts_count makes the unsigned tts_count - 1 loop bound wrap to UINT_MAX, and the loop indexes a NULL tts_data array. Processing a MOV-family file with that empty timing state is required; FFmpeg states that no released version was ever affected.
The record
- CVE
- CVE-2025-25471
- Published
- Feb 18, 2025
- Updated
- Feb 20, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Feb 18, 2025CVE publishedPublication date reported by the CVE source.
- Feb 20, 2025Record 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
No public exploit references are available in this record.
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