Skip to content
Fencer Intel
medium 6.5

CVE-2019-1000016 json

FFMPEG version 4.1 contains a CWE-129: Improper Validation of Array Index vulnerability in...

published 7y ago modified 3mo ago also EUVD-2019-1735 , JLSEC-2025-101

cvss
6.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.1%
EPSS 1.1% chance of exploitation in 30 days, percentile 66%
public exploits
0
none known

Summary

FFMPEG version 4.1 contains a CWE-129: Improper Validation of Array Index vulnerability in libavcodec/cbs_av1.c that can result in Denial of service. This attack appears to be exploitable via specially crafted AV1 file has to be provided as input. This vulnerability appears to have been fixed in after commit b97a4b658814b2de8b9f2a3bce491c002d34de31.

Patch / fix

  • julia FFMPEG_jll 4.3.1+0
  • ffmpeg Debian 14, Debian 13, Debian 12 7:4.1.1-1

debian advisories DEBIAN-CVE-2019-1000016

  • ffmpeg Alpine 3.24, Alpine 3.23, Alpine 3.22 +12 more 4.1.1-r0
  • ffmpeg4 Alpine 3.22, Alpine 3.21, Alpine 3.20 +4 more 4.1.1-r0

alpine advisories ALPINE-CVE-2019-1000016

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2019-1000016 in your dependencies? 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.12% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 6.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P
OSV 3.0 6.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
julia FFMPEG_jll
<4.3.1+0
4.3.1+0

Classification

Weakness
  • CWE-129 Improper Validation of Array Index

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.