First published: Sun Oct 02 2011(Updated: )
Integer signedness error in the decode_residual_block function in cavsdec.c in libavcodec in FFmpeg before 0.7.3 and 0.8.x before 0.8.2, and libav through 0.7.1, allows remote attackers to cause a denial of service (memory corruption and application crash) or possibly execute arbitrary code via a crafted Chinese AVS video (aka CAVS) file.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
FFmpeg | =0.7.1 | |
FFmpeg | =0.4.5 | |
FFmpeg | =0.3.2 | |
FFmpeg | =0.4.7 | |
FFmpeg | =0.6.1 | |
FFmpeg | =0.3.3 | |
FFmpeg | =0.3 | |
FFmpeg | =0.4.2 | |
FFmpeg | <=0.7.2 | |
FFmpeg | =0.5 | |
FFmpeg | =0.5.4 | |
FFmpeg | =0.5.1 | |
FFmpeg | =0.3.1 | |
FFmpeg | =0.4.9-pre1 | |
FFmpeg | =0.6 | |
FFmpeg | =0.5.3 | |
FFmpeg | =0.4.4 | |
FFmpeg | =0.5.2 | |
FFmpeg | =0.4.6 | |
FFmpeg | =0.3.4 | |
FFmpeg | =0.4.0 | |
FFmpeg | =0.6.2 | |
FFmpeg | =0.4.8 | |
FFmpeg | =0.4.3 | |
FFmpeg | =0.8.0 | |
FFmpeg | =0.8.1 | |
libavutil | =0.4.1 | |
libavutil | =0.4.7 | |
libavutil | =0.3.3 | |
libavutil | =0.7-beta2 | |
libavutil | =0.4.8 | |
libavutil | =0.6.2 | |
libavutil | =0.5 | |
libavutil | =0.4.4 | |
libavutil | <=0.7.1 | |
libavutil | =0.4.9-pre1 | |
libavutil | =0.4.5 | |
libavutil | =0.5.4 | |
libavutil | =0.3.1 | |
libavutil | =0.4.3 | |
libavutil | =0.4.2 | |
libavutil | =0.3 | |
libavutil | =0.3.2 | |
libavutil | =0.4.6 | |
libavutil | =0.6.1 | |
libavutil | =0.4.0 | |
libavutil | =0.3.4 | |
libavutil | =0.6 | |
libavutil | =0.7-beta1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2011-3362 is classified as a denial of service vulnerability that can potentially lead to memory corruption and application crashes.
To fix CVE-2011-3362, upgrade FFmpeg to version 0.7.3 or later, or update Libav to version 0.7.2 or later.
CVE-2011-3362 affects FFmpeg versions before 0.7.3 and 0.8.x before 0.8.2, as well as Libav versions through 0.7.1.
The potential impacts of CVE-2011-3362 include application crashes and the possibility of executing arbitrary code by remote attackers.
While CVE-2011-3362 is outdated, it may still pose a risk for legacy software systems that have not been updated.