Skip to content
Fencer Intel
medium 6.5

CVE-2017-14059 json

In FFmpeg 3.3.3, a DoS in cine_read_header() due to lack of an EOF check might cause huge CPU and memory consumption.

published 2017-08-31 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-5573

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

Summary

In FFmpeg 3.3.3, a DoS in cine_read_header() due to lack of an EOF check might cause huge CPU and memory consumption. When a crafted CINE file, which claims a large "duration" field in the header but does not contain sufficient backing data, is provided, the image-offset parsing loop would consume huge CPU and memory resources, since there is no EOF check inside the loop.

Patch / fix

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

debian advisories DEBIAN-CVE-2017-14059

  • ffmpeg Ubuntu 16.04 LTS 7:2.8.14-0ubuntu0.16.04.1

ubuntu advisories UBUNTU-CVE-2017-14059

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-4 openSUSE Tumbleweed 4.4-5.2

opensuse advisories openSUSE-SU-2024:10754-1

  • ffmpeg Alpine 3.24, Alpine 3.23, Alpine 3.22 +15 more 3.3.4-r0
  • ffmpeg Alpine 3.5, Alpine 3.4 3.1.11-r0
  • ffmpeg Alpine 3.6 3.2.8-r0
  • ffmpeg4 Alpine 3.22, Alpine 3.21, Alpine 3.20 +4 more 3.3.4-r0

alpine advisories ALPINE-CVE-2017-14059

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

  • ffmpeg Arch Linux 1:3.3.4-1

arch linux advisories AVG-400

Exploit prediction

1.78% chance of exploitation in the next 30 days, higher than 78% 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 7.1 AV:N/AC:M/Au:N/C:N/I:N/A:C

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.