Memory corruption via one-pixel frame width underflow
Published May 27, 2021 · Updated Aug 4, 2024
Heap-based buffer overflow in FFmpeg 4.2 allows remote attackers to corrupt memory by processing a crafted one-pixel-wide video frame. The neighbor filter's filter_slice function passes width minus two to deflate16 when the frame width is one, causing accesses outside the allocated heap buffer. Exploitation requires processing attacker-controlled media and can crash the FFmpeg process through memory corruption; public sources do not establish code execution.
Summary
What happened
Heap-based buffer overflow in FFmpeg 4.2 allows remote attackers to corrupt memory by processing a crafted one-pixel-wide video frame. The neighbor filter's filter_slice function passes width minus two to deflate16 when the frame width is one, causing accesses outside the allocated heap buffer. Exploitation requires processing attacker-controlled media and can crash the FFmpeg process through memory corruption; public sources do not establish code execution.
The record
- CVE
- CVE-2020-22027
- 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.
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 8242 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