First published: Wed Feb 27 2013(Updated: )
The avcodec_decode_audio4 function in utils.c in libavcodec in FFmpeg before 1.1.3 does not verify the decoding state before proceeding with certain skip operations, which allows remote attackers to cause a denial of service (out-of-bounds array access and application crash) or possibly have unspecified other impact via crafted audio data.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
FFmpeg | <=1.1.2 | |
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 | |
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.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 | |
FFmpeg | =0.9.1 | |
FFmpeg | =0.10 | |
FFmpeg | =0.10.3 | |
FFmpeg | =0.10.4 | |
FFmpeg | =0.11 | |
FFmpeg | =1.0 | |
FFmpeg | =1.1.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2013-2276 has a medium severity level as it can cause denial of service through application crashes.
CVE-2013-2276 affects multiple versions of FFmpeg, specifically versions prior to 1.1.3.
To fix CVE-2013-2276, update FFmpeg to version 1.1.3 or later.
Users may experience application crashes leading to service disruptions due to CVE-2013-2276.
Yes, CVE-2013-2276 is exploitable remotely, allowing attackers to potentially trigger the denial of service.