First published: Thu Feb 09 2017(Updated: )
Heap-based buffer overflow in libavformat/rtmppkt.c in FFmpeg before 2.8.10, 3.0.x before 3.0.5, 3.1.x before 3.1.6, and 3.2.x before 3.2.2 allows remote attackers to execute arbitrary code by leveraging failure to check for RTMP packet size mismatches.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
FFmpeg | <=2.8.9 | |
FFmpeg | =3.0 | |
FFmpeg | =3.0.1 | |
FFmpeg | =3.0.2 | |
FFmpeg | =3.0.3 | |
FFmpeg | =3.0.4 | |
FFmpeg | =3.1 | |
FFmpeg | =3.1.1 | |
FFmpeg | =3.1.2 | |
FFmpeg | =3.1.3 | |
FFmpeg | =3.1.4 | |
FFmpeg | =3.1.5 | |
FFmpeg | =3.2 | |
FFmpeg | =3.2.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-10191 is classified as a critical vulnerability due to the potential for remote code execution.
To fix CVE-2016-10191, upgrade to FFmpeg version 2.8.10 or later, or 3.0.5 or later, 3.1.6 or later, or 3.2.2 or later.
CVE-2016-10191 affects multiple versions of FFmpeg, specifically all versions prior to 2.8.10, 3.0.5, 3.1.6, and 3.2.2.
CVE-2016-10191 can allow remote attackers to execute arbitrary code on affected systems by exploiting the heap-based buffer overflow.
Yes, CVE-2016-10191 is exploitable remotely, making it particularly dangerous for systems exposed to untrusted networks.