Process crash via incorrect 16-bit loop bound
Published May 26, 2021 · Updated Aug 4, 2024
A heap-buffer overflow in FFmpeg 4.2's lagfun video filter allows remote attackers to crash the process via crafted media. The lagfun_frame16 loop treats a byte-count linesize as a uint16_t element count, iterating twice past the intended row buffer. Processing attacker-supplied media through the 16-bit lagfun path and user interaction are required; the reported consequence is process termination.
Summary
What happened
A heap-buffer overflow in FFmpeg 4.2's lagfun video filter allows remote attackers to crash the process via crafted media. The lagfun_frame16 loop treats a byte-count linesize as a uint16_t element count, iterating twice past the intended row buffer. Processing attacker-supplied media through the 16-bit lagfun path and user interaction are required; the reported consequence is process termination.
The record
- CVE
- CVE-2020-22024
- Published
- May 26, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 26, 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.
Weakness, pattern, technique
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