First published: Mon Dec 09 2013(Updated: )
The dirac_decode_data_unit function in libavcodec/diracdec.c in FFmpeg before 0.10 allows remote attackers to have an unspecified impact via a crafted value in the reference pictures number.
Credit: cve-coordination@google.com
Affected Software | Affected Version | How to fix |
---|---|---|
FFmpeg | =0.7.7 | |
FFmpeg | =0.7.1 | |
FFmpeg | =0.7.6 | |
FFmpeg | =0.4.5 | |
FFmpeg | =0.3.2 | |
FFmpeg | =0.8.6 | |
FFmpeg | =0.4.7 | |
FFmpeg | =0.6.1 | |
FFmpeg | =0.3.3 | |
FFmpeg | =0.7.5 | |
FFmpeg | =0.5.4.6 | |
FFmpeg | =0.3 | |
FFmpeg | =0.4.2 | |
FFmpeg | =0.5 | |
FFmpeg | =0.5.4 | |
FFmpeg | =0.8.5.4 | |
FFmpeg | =0.8.5.3 | |
FFmpeg | =0.5.1 | |
FFmpeg | =0.8.5 | |
FFmpeg | =0.9 | |
FFmpeg | =0.3.1 | |
FFmpeg | =0.7.3 | |
FFmpeg | =0.4.9-pre1 | |
FFmpeg | =0.7.4 | |
FFmpeg | =0.8.0 | |
FFmpeg | =0.5.5 | |
FFmpeg | =0.6 | |
FFmpeg | =0.5.3 | |
FFmpeg | =0.8.10 | |
FFmpeg | =0.4.4 | |
FFmpeg | =0.5.2 | |
FFmpeg | <=0.9.1 | |
FFmpeg | =0.4.6 | |
FFmpeg | =0.3.4 | |
FFmpeg | =0.7.8 | |
FFmpeg | =0.4.0 | |
FFmpeg | =0.6.2 | |
FFmpeg | =0.8.7 | |
FFmpeg | =0.7.9 | |
FFmpeg | =0.5.4.5 | |
FFmpeg | =0.7 | |
FFmpeg | =0.7.12 | |
FFmpeg | =0.8.1 | |
FFmpeg | =0.4.8 | |
FFmpeg | =0.4.3 | |
FFmpeg | =0.6.3 | |
FFmpeg | =0.8.11 | |
FFmpeg | =0.8.8 | |
FFmpeg | =0.8.2 | |
FFmpeg | =0.7.11 | |
FFmpeg | =0.7.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2011-3950 is high due to the potential for arbitrary code execution that can be triggered by a specially crafted input.
To fix CVE-2011-3950, upgrade to FFmpeg version 0.10 or later, which contains the necessary patches.
FFmpeg versions before 0.10, including 0.7.x, 0.8.x, and earlier releases, are affected by CVE-2011-3950.
CVE-2011-3950 can allow remote attackers to potentially execute arbitrary code on the affected system.
There are no known effective workarounds for CVE-2011-3950, so upgrading is strongly recommended.