Vulnerabilities · 2017 · Ffmpeg
CVE-2017-14170
Ffmpeg vulnerability
In libavformat/mxfdec.c in FFmpeg 3.3.3 -> 2.4, a DoS in mxf_read_index_entry_array() due to lack of an EOF (End of File) check might cause huge CPU consumption. When a crafted MXF file, which claims a large "nb_index_entries" field in the header but does not contain sufficient backing data, is provided, the loop would consume huge CPU resources, since there is no EOF check inside the loop. Moreover, this big loop can be invoked multiple times if there is more than one applicable data segment in the crafted MXF file.
Affected products
Ffmpeg. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Ffmpeg runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/FFmpeg/FFmpeg/commit/900f39692ca0337a98a7cf047e4e2611071810c2 · Patch
- www.debian.org/security/2017/dsa-3996
- www.securityfocus.com/bid/100700
- github.com/FFmpeg/FFmpeg/commit/f173cdfe669556aa92857adafe60cbe5f2aa1210
- lists.debian.org/debian-lts-announce/2019/01/msg00006.html
- nvd.nist.gov/vuln/detail/CVE-2017-14170
- cve.org/CVERecord?id=CVE-2017-14170
More vulnerabilities in Ffmpeg products
CVE-2025-63757CVE-2025-25469CVE-2025-25468CVE-2025-22921CVE-2025-1594CVE-2025-1373CVE-2025-0518CVE-2024-55069All 474
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.