Memory corruption via undersized w3fdif video
Published May 27, 2021 · Updated Aug 4, 2024
Heap-based buffer overflow in FFmpeg 4.2 allows remote attackers to corrupt memory via a crafted video processed by the w3fdif filter. The w3fdif configuration path fails to reject inputs under three lines before filter16_complex_low processes them, causing an out-of-bounds heap write. Processing the crafted video with w3fdif and user interaction are required; public records establish memory corruption but no more specific consequence.
Summary
What happened
Heap-based buffer overflow in FFmpeg 4.2 allows remote attackers to corrupt memory via a crafted video processed by the w3fdif filter. The w3fdif configuration path fails to reject inputs under three lines before filter16_complex_low processes them, causing an out-of-bounds heap write. Processing the crafted video with w3fdif and user interaction are required; public records establish memory corruption but no more specific consequence.
The record
- CVE
- CVE-2020-22031
- Published
- May 27, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 27, 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.
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