Skip to content
Fencer Intel
medium 5.5

CVE-2016-1897 json

FFmpeg 2.x allows remote attackers to conduct cross-origin attacks and read arbitrary files by using the concat protocol in an HTTP Live St…

published 2016-01-15 10 y ago modified 2026-06-17 4 mo ago also EUVD-2016-2991

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

Summary

FFmpeg 2.x allows remote attackers to conduct cross-origin attacks and read arbitrary files by using the concat protocol in an HTTP Live Streaming (HLS) M3U8 file, leading to an external HTTP request in which the URL string contains the first line of a local file.

Patch / fix

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

debian advisories DEBIAN-CVE-2016-1897

  • ffmpeg Ubuntu 16.04 LTS 7:2.8.6-1ubuntu1
  • libav Ubuntu Pro 14.04 LTS 6:9.20-0ubuntu0.14.04.1+esm1

ubuntu advisories UBUNTU-CVE-2016-1897

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

Exploit prediction

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

Exploits and checks

  • security.stackexchange.com http://security.stackexchange.com/questions/110644 referenced PoC, tagged "exploit" by a source, unverified
  • habrahabr.ru http://habrahabr.ru/company/mailru/blog/274855 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

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.