Skip to content
Fencer Intel
medium 6.5

CVE-2017-14058 json

In FFmpeg 2.4 and 3.3.3, the read_data function in libavformat/hls.c does not restrict reload attempts for an insufficient list, which allo…

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

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

Summary

In FFmpeg 2.4 and 3.3.3, the read_data function in libavformat/hls.c does not restrict reload attempts for an insufficient list, which allows remote attackers to cause a denial of service (infinite loop).

Patch / fix

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

debian advisories DEBIAN-CVE-2017-14058

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

ubuntu advisories UBUNTU-CVE-2017-14058

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

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

2.17% chance of exploitation in the next 30 days, higher than 82% 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

Classification

Weakness
  • CWE-835 Loop with Unreachable Exit Condition

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.