Application crash via undersized Gaussian-blur buffer
Published Sep 20, 2021 · Updated Aug 4, 2024
Heap-buffer overflow in FFmpeg 4.2.1 allows remote attackers to crash media-processing applications via crafted video input. The gblur filter's config_input function allocates width-by-height storage even though SIMD routines access dimensions rounded to 16-byte boundaries. Exploitation requires an application to process attacker-supplied media with the gblur filter; the bounded reported consequence is a crash.
Summary
What happened
Heap-buffer overflow in FFmpeg 4.2.1 allows remote attackers to crash media-processing applications via crafted video input. The gblur filter's config_input function allocates width-by-height storage even though SIMD routines access dimensions rounded to 16-byte boundaries. Exploitation requires an application to process attacker-supplied media with the gblur filter; the bounded reported consequence is a crash.
The record
- CVE
- CVE-2020-20891
- Published
- Sep 20, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 20, 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