Skip to content
Fencer Intel
critical 9.8

CVE-2019-12730 json

aa_read_header in libavformat/aadec.c in FFmpeg before 3.2.14 and 4.x before 4.1.4 does not check for sscanf failure and consequently allow…

published 7y ago modified 4mo ago also EUVD-2019-4320

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

Summary

aa_read_header in libavformat/aadec.c in FFmpeg before 3.2.14 and 4.x before 4.1.4 does not check for sscanf failure and consequently allows use of uninitialized variables.

Patch / fix

  • ffmpeg ffmpeg 3.2.14
  • ffmpeg Debian 14, Debian 13, Debian 12 7:4.1.4-1

debian advisories DEBIAN-CVE-2019-12730

  • ffmpeg Ubuntu 16.04 LTS 7:2.8.17-0ubuntu0.1
  • ffmpeg Ubuntu 18.04 LTS 7:3.4.8-0ubuntu0.2

ubuntu advisories UBUNTU-CVE-2019-12730

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 SLE Workstation Extension 15 SP1, SLE Workstation Extension 15, SLE Module for Package Hub 15 SP1 +3 more 3.4.2-4.27.1

suse advisories SUSE-SU-2019:3184-2SUSE-SU-2019:3184-1

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

alpine advisories ALPINE-CVE-2019-12730

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-12730 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

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

CVSS scores

assigned by version score vector
NVD 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-908 Use of Uninitialized Resource

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.