CVE-2020-22016
HIGHCVSS 8.8/10EPSS 1.59%
Last modified
CVE-2020-22016 is a high-severity vulnerability rated 8.8/10 on the CVSS scale. A heap-based Buffer Overflow vulnerability in FFmpeg 4.2 at libavcodec/get_bits.h when writing .mov files, which might lead to memory corruption and other potential consequences.. EPSS estimates a 1.59% chance of exploitation in the next 30 days.
Description
A heap-based Buffer Overflow vulnerability in FFmpeg 4.2 at libavcodec/get_bits.h when writing .mov files, which might lead to memory corruption and other potential consequences.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Ffmpeg | Ffmpeg | 4.2 |
| Debian | Debian Linux | 9.0 |
| Debian | Debian Linux | 10.0 |
References
- https://lists.debian.org/debian-lts-announce/2021/08/msg00018.htmlMailing List, Third Party Advisory
- https://trac.ffmpeg.org/ticket/8183Exploit, Issue Tracking, Vendor Advisory
- https://www.debian.org/security/2021/dsa-4990Third Party Advisory
- https://lists.debian.org/debian-lts-announce/2021/08/msg00018.htmlMailing List, Third Party Advisory
- https://trac.ffmpeg.org/ticket/8183Exploit, Issue Tracking, Vendor Advisory
- https://www.debian.org/security/2021/dsa-4990Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2020-22016?
A heap-based Buffer Overflow vulnerability in FFmpeg 4.2 at libavcodec/get_bits.h when writing .mov files, which might lead to memory corruption and other potential consequences.
How severe is CVE-2020-22016?
CVE-2020-22016 has a CVSS score of 8.8/10 (HIGH severity). The EPSS model estimates a 1.59% probability of exploitation in the next 30 days.
How do I fix CVE-2020-22016?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
Are you affected by CVE-2020-22016?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
