Quick answers
- Is CVE-2016-6164 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2016-6164 being exploited in the wild.
- How severe is CVE-2016-6164?
- Critical severity, with a CVSS score of 9.8, published 23 January 2017.
- Which products and versions are affected?
- Ffmpeg before 2.8.8, 3.0.x before 3.0.3, 3.1.x before 3.1.1.
- Is there a fix for CVE-2016-6164?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2016-6164 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2016-6164?
- Check whether you run Ffmpeg at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An integer overflow vulnerability exists in the mov_build_index function in libavformat/mov.c in FFmpeg. The flaw is triggered by improper handling of sample size values within MOV files. A remote attacker can exploit this by providing a specially crafted media file that, when processed, causes an integer overflow. This can lead to unspecified impacts, typically including heap-based buffer overflows or memory corruption, potentially allowing for arbitrary code execution or a denial-of-service (DoS) condition. The vulnerability is reachable over the network without authentication or user interaction beyond the application opening the malicious file. The issue was addressed in FFmpeg versions 2.8.8, 3.0.3, and 3.1.1.
Affected products
- FFmpeg FFmpeg before 2.8.8, 3.0.x before 3.0.3, 3.1.x before 3.1.1
Timeline
- 2017-01-23: advisory: NVD publication date