Skip to content
Fencer Intel
medium 6.5

CVE-2017-14057 json

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

published 9y ago modified 4mo ago also EUVD-2017-5571

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 asf_read_marker() due to lack of an EOF (End of File) check might cause huge CPU and memory consumption. When a crafted ASF file, which claims a large "name_len" or "count" field in the header but does not contain sufficient backing data, is provided, the loops over the name and markers would consume huge CPU and memory resources, since there is no EOF check inside these loops.

Patch / fix

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

debian advisories DEBIAN-CVE-2017-14057

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

ubuntu advisories UBUNTU-CVE-2017-14057

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

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

Is CVE-2017-14057 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.81% 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.