Memory corruption via unpadded MOV track extradata
Published May 27, 2021 · Updated Aug 4, 2024
Heap-based buffer overflow in FFmpeg 4.2 allows attackers to corrupt memory when crafted codec data is written to a MOV file. In libavformat/movenc.c, MOV-writing paths copied codec extradata into exactly sized track buffers without the zero padding required by bit readers, allowing access beyond the allocation. Exploitation requires a user or application to process attacker-controlled media into MOV output; the demonstrated consequence is a crash, while further impact is unspecified.
Summary
What happened
Heap-based buffer overflow in FFmpeg 4.2 allows attackers to corrupt memory when crafted codec data is written to a MOV file. In libavformat/movenc.c, MOV-writing paths copied codec extradata into exactly sized track buffers without the zero padding required by bit readers, allowing access beyond the allocation. Exploitation requires a user or application to process attacker-controlled media into MOV output; the demonstrated consequence is a crash, while further impact is unspecified.
The record
- CVE
- CVE-2020-22016
- Published
- May 27, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- 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
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