Memory corruption via undersized bwdif frames
Published Jun 1, 2021 · Updated Aug 4, 2024
Heap-based buffer overflow in FFmpeg 4.2's bwdif video filter allows remote attackers to corrupt memory via crafted video input. The config_props height check admits three-line frames even though filter_intra requires at least four lines, producing an out-of-bounds heap write. Exploitation requires processing attacker-supplied video with the bwdif filter and user interaction; the documented consequence is memory corruption.
Summary
What happened
Heap-based buffer overflow in FFmpeg 4.2's bwdif video filter allows remote attackers to corrupt memory via crafted video input. The config_props height check admits three-line frames even though filter_intra requires at least four lines, producing an out-of-bounds heap write. Exploitation requires processing attacker-supplied video with the bwdif filter and user interaction; the documented consequence is memory corruption.
The record
- CVE
- CVE-2020-22036
- Published
- Jun 1, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 1, 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.
Public exploit references
- FFmpeg ticket 8261 reproducerproof 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