Skip to content
Fencer Intel
medium 6.5

CVE-2019-13390 json

In FFmpeg 4.1.3, there is a division by zero at adx_write_trailer in libavformat/rawenc.c.

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

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

Summary

In FFmpeg 4.1.3, there is a division by zero at adx_write_trailer in libavformat/rawenc.c.

Patch / fix

  • ffmpeg Debian 14, Debian 13, Debian 12 7:4.2.1-1

debian advisories DEBIAN-CVE-2019-13390

  • 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-13390

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 15 SP1-LTSS, SLE High Performance Computing 15 SP1-LTSS +1 more 3.4.2-150000.4.53.2
  • ffmpeg SLE Workstation Extension 15 SP4, SLE Real Time 15 SP3, SLE Module for Package Hub 15 SP4 +2 more 3.4.2-150200.11.25.1

suse advisories SUSE-SU-2023:2115-1SUSE-SU-2023:0206-1

  • ffmpeg Alpine 3.9 4.0.6-r0

alpine advisories ALPINE-CVE-2019-13390

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-13390 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.71% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

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

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

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.