Skip to content
Fencer Vulns
medium 6.6

CVE-2024-32228 json

FFmpeg 7.0 is vulnerable to Buffer Overflow.

published 2024-07-01 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-30047

cvss
6.6
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 16%
public exploits
0
none known

Summary

FFmpeg 7.0 is vulnerable to Buffer Overflow. There is a SEGV at libavcodec/hevcdec.c:2947:22 in hevc_frame_end.

Patch / fix

  • ffmpeg Debian 14, Debian 13 7:7.0.1-3

debian advisories DEBIAN-CVE-2024-32228

  • ffmpeg-6 openSUSE Tumbleweed 6.1.1-6.1
  • ffmpeg-5 openSUSE Tumbleweed 5.1.4-9.1
  • ffmpeg-7 openSUSE Tumbleweed 7.0-2.1

opensuse advisories openSUSE-SU-2024:14226-1openSUSE-SU-2024:14221-1openSUSE-SU-2024:14097-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-32228 updated cvss 6.6

ffmpeg: Buffer Overflow

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.25% chance of exploitation in the next 30 days, higher than 16% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • trac.ffmpeg.org https://trac.ffmpeg.org/ticket/10951 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CISA ADP 3.1 6.6 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H
CNA 3.1 6.6 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H

Affected products

  • ffmpeg ffmpeg

Classification

Weakness
  • CWE-120 Buffer Copy without Checking Size of Input
  • CWE-121 Stack-based Buffer Overflow

References

Sources

Fencer Vulns 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.