Out-of-bounds write via signed tile-offset overflow
Published Feb 19, 2024 · Updated Feb 13, 2025
Integer overflow in VideoLAN dav1d before 1.4.0 allows attackers to write outside decoder memory through oversized AV1 frame dimensions. In dav1d_decode_frame_init, multithreaded tile offsets were accumulated in signed 32-bit fields and then used to derive writable pointers. The path requires multithreaded decoding on a 64-bit build without a restrictive frame-size limit; high-bit-depth input can place corrupted pointers within normal address ranges.
Summary
What happened
Integer overflow in VideoLAN dav1d before 1.4.0 allows attackers to write outside decoder memory through oversized AV1 frame dimensions. In dav1d_decode_frame_init, multithreaded tile offsets were accumulated in signed 32-bit fields and then used to derive writable pointers. The path requires multithreaded decoding on a 64-bit build without a restrictive frame-size limit; high-bit-depth input can place corrupted pointers within normal address ranges.
The record
- CVE
- CVE-2024-1580
- Published
- Feb 19, 2024
- Updated
- Feb 13, 2025
- Vendor
- VideoLAN
- Product
- dav1d
- Classifications
- CWE-190, T1203
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 19, 2024CVE publishedPublication date reported by the CVE source.
- Feb 13, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.4.0
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
Public exploit references
- Project Zero poc1.obu and poc2.obu test casesproof 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