First published: Mon Dec 09 2013(Updated: )
The decode_mb function in libavcodec/error_resilience.c in FFmpeg before 0.10 allows remote attackers to have an unspecified impact via vectors related to an uninitialized block index, which triggers an out-of-bounds write.
Credit: cve-coordination@google.com
Affected Software | Affected Version | How to fix |
---|---|---|
FFmpeg | <=0.9.1 | |
FFmpeg | =0.3 | |
FFmpeg | =0.3.1 | |
FFmpeg | =0.3.2 | |
FFmpeg | =0.3.3 | |
FFmpeg | =0.3.4 | |
FFmpeg | =0.4.0 | |
FFmpeg | =0.4.2 | |
FFmpeg | =0.4.3 | |
FFmpeg | =0.4.4 | |
FFmpeg | =0.4.5 | |
FFmpeg | =0.4.6 | |
FFmpeg | =0.4.7 | |
FFmpeg | =0.4.8 | |
FFmpeg | =0.4.9-pre1 | |
FFmpeg | =0.5 | |
FFmpeg | =0.5.1 | |
FFmpeg | =0.5.2 | |
FFmpeg | =0.5.3 | |
FFmpeg | =0.5.4 | |
FFmpeg | =0.5.4.5 | |
FFmpeg | =0.5.4.6 | |
FFmpeg | =0.5.5 | |
FFmpeg | =0.6 | |
FFmpeg | =0.6.1 | |
FFmpeg | =0.6.2 | |
FFmpeg | =0.6.3 | |
FFmpeg | =0.7 | |
FFmpeg | =0.7.1 | |
FFmpeg | =0.7.2 | |
FFmpeg | =0.7.3 | |
FFmpeg | =0.7.4 | |
FFmpeg | =0.7.5 | |
FFmpeg | =0.7.6 | |
FFmpeg | =0.7.7 | |
FFmpeg | =0.7.8 | |
FFmpeg | =0.7.9 | |
FFmpeg | =0.7.11 | |
FFmpeg | =0.7.12 | |
FFmpeg | =0.8.0 | |
FFmpeg | =0.8.1 | |
FFmpeg | =0.8.2 | |
FFmpeg | =0.8.5 | |
FFmpeg | =0.8.5.3 | |
FFmpeg | =0.8.5.4 | |
FFmpeg | =0.8.6 | |
FFmpeg | =0.8.7 | |
FFmpeg | =0.8.8 | |
FFmpeg | =0.8.10 | |
FFmpeg | =0.8.11 | |
FFmpeg | =0.9 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2011-3941 is classified as a vulnerability that may allow remote attackers to impact the application through an out-of-bounds write.
To fix CVE-2011-3941, update FFmpeg to version 0.10 or later, where the vulnerability is addressed.
CVE-2011-3941 affects multiple versions of FFmpeg prior to 0.10, including versions 0.3 to 0.9.1.
CVE-2011-3941 can lead to undefined behavior, crashes, or potential code execution by an attacker through manipulated video files.
Yes, using FFmpeg 0.10 or later will mitigate the risk associated with CVE-2011-3941 since the vulnerability has been resolved.