Skip to content
Fencer Intel
high 8.8

CVE-2020-22023 json

A heap-based Buffer Overflow vulnerabililty exists in FFmpeg 4.2 in filter_frame at libavfilter/vf_bitplanenoise.c, which might lead to mem…

published 5y ago modified 4mo ago also EUVD-2020-14789

cvss
8.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.5%
EPSS 1.5% chance of exploitation in 30 days, percentile 73%
public exploits
0
none known

Summary

A heap-based Buffer Overflow vulnerabililty exists in FFmpeg 4.2 in filter_frame at libavfilter/vf_bitplanenoise.c, which might lead to memory corruption and other potential consequences.

Patch / fix

  • ffmpeg Debian 14, Debian 13, Debian 12 7:4.3-2

debian advisories DEBIAN-CVE-2020-22023

  • ffmpeg Ubuntu 18.04 LTS 7:3.4.11-0ubuntu0.1
  • ffmpeg Ubuntu 20.04 LTS 7:4.2.7-0ubuntu0.1

ubuntu advisories UBUNTU-CVE-2020-22023

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • ffmpeg SLES for SAP 15 SP1, SLES for SAP 15, SLES 15-LTSS +10 more 3.4.2-4.34.2
  • ffmpeg SLE Workstation Extension 15 SP3, SLE Workstation Extension 15 SP2, SLE Module for Package Hub 15 SP3 +3 more 3.4.2-11.3.1

suse advisories SUSE-SU-2021:2929-1SUSE-SU-2021:2322-1

  • ffmpeg openSUSE Leap 15.3 3.4.2-11.3.1

opensuse advisories openSUSE-SU-2021:2322-1

Is CVE-2020-22023 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.46% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.