CVE-2020-22015: Buffer Overflow
First published: Wed May 26 2021(Updated: )
Buffer Overflow vulnerability in FFmpeg 4.2 in mov_write_video_tag due to the out of bounds in libavformat/movenc.c, which could let a remote malicious user obtain sensitive information, cause a Denial of Service, or execute arbitrary code.
Credit: cve@mitre.org cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| FFmpeg FFmpeg | =4.2 | |
| Debian Debian Linux | =9.0 | |
| Debian Debian Linux | =10.0 | |
| debian/ffmpeg | 7:4.3.7-0+deb11u1 7:5.1.6-0+deb12u1 7:7.0.2-3 |
Remedy
https://git.videolan.org/?p=ffmpeg.git;a=commitdiff;h=4c1afa292520329eecd1cc7631bc59a8cca95c46
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://trac.ffmpeg.org/ticket/8190
- https://lists.debian.org/debian-lts-announce/2021/08/msg00018.html
- https://www.debian.org/security/2021/dsa-4990
- https://launchpad.net/bugs/cve/CVE-2020-22015
- https://git.videolan.org/?p=ffmpeg.git;a=commitdiff;h=4c1afa292520329eecd1cc7631bc59a8cca95c46
- https://security-tracker.debian.org/tracker/CVE-2020-22015
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-22015
- https://nvd.nist.gov/vuln/detail/CVE-2020-22015
- https://ubuntu.com/security/CVE-2020-22015
Frequently Asked Questions
What is CVE-2020-22015?
CVE-2020-22015 is a buffer overflow vulnerability in FFmpeg 4.2 in mov_write_video_tag due to the out of bounds in libavformat/movenc.c.
What is the impact of CVE-2020-22015?
The impact of CVE-2020-22015 includes the potential for a remote malicious user to obtain sensitive information, cause a Denial of Service, or execute arbitrary code.
Which software versions are affected by CVE-2020-22015?
FFmpeg versions up to and including 4.4.1, 7:3.4.11-0ubuntu0.1, 7:4.2.7-0ubuntu0.1, 7:4.4.2-0ubuntu0.21.10.1, and 7:4.1.9-0+deb10u1, 7:4.1.11-0+deb10u1, 7:4.3.6-0+deb11u1, 7:5.1.3-1, 7:6.0-7 are affected by CVE-2020-22015.
How can I verify if I am using an affected version of FFmpeg?
You can check your FFmpeg version by running 'ffmpeg -version' command in the terminal.
How do I fix CVE-2020-22015?
To fix CVE-2020-22015, you should update FFmpeg to version 4.4.1 or later, or apply the available security patches for your specific distribution.
- agent/type
- agent/first-publish-date
- collector/launchpad-cve
- source/Launchpad
- agent/author
- agent/severity
- agent/remedy
- agent/weakness
- agent/description
- agent/references
- collector/nvd-cve
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/nvd-index
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/tags
- agent/event
- collector/security-tracker-debian
- source/Debian
- agent/softwarecombine
- collector/usn-cve
- source/Ubuntu
- vendor/ffmpeg
- canonical/ffmpeg ffmpeg
- version/ffmpeg ffmpeg/4.2
- vendor/debian
- canonical/debian debian linux
- version/debian debian linux/9.0
- version/debian debian linux/10.0
- package-manager/debian