Application crash via inconsistent packet queue pointers
Published Aug 10, 2021 · Updated Aug 4, 2024
A heap use-after-free in FFmpeg 4.2 allows remote attackers to crash media-processing applications via a crafted AVI file. The mpeg_mux_write_packet function can create two packet queues when premux_packet is null while predecode_packet is not, leaving a stale pointer to freed queue storage. Exploitation requires an application to process attacker-supplied AVI content and interrupts only that application; no data disclosure or modification is reported.
Summary
What happened
A heap use-after-free in FFmpeg 4.2 allows remote attackers to crash media-processing applications via a crafted AVI file. The mpeg_mux_write_packet function can create two packet queues when premux_packet is null while predecode_packet is not, leaving a stale pointer to freed queue storage. Exploitation requires an application to process attacker-supplied AVI content and interrupts only that application; no data disclosure or modification is reported.
The record
- CVE
- CVE-2020-21697
- Published
- Aug 10, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 10, 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.
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