CVE-2011-3950: Medium severity ffmpeg vulnerability
Published Dec 9, 2013
·Updated
The diracdecodedataunit 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.
Affected Software
51 affected components
FFmpeg FFmpeg=0.7.7
FFmpeg FFmpeg=0.7.1
FFmpeg FFmpeg=0.7.6
FFmpeg FFmpeg=0.4.5
FFmpeg FFmpeg=0.3.2
FFmpeg FFmpeg=0.8.6
FFmpeg FFmpeg=0.4.7
FFmpeg FFmpeg=0.6.1
FFmpeg FFmpeg=0.3.3
FFmpeg FFmpeg=0.7.5
FFmpeg FFmpeg=0.5.4.6
FFmpeg FFmpeg=0.3
FFmpeg FFmpeg=0.4.2
FFmpeg FFmpeg=0.5
FFmpeg FFmpeg=0.5.4
FFmpeg FFmpeg=0.8.5.4
FFmpeg FFmpeg=0.8.5.3
FFmpeg FFmpeg=0.5.1
FFmpeg FFmpeg=0.8.5
FFmpeg FFmpeg=0.9
FFmpeg FFmpeg=0.3.1
FFmpeg FFmpeg=0.7.3
FFmpeg FFmpeg=0.4.9-pre1
FFmpeg FFmpeg=0.7.4
FFmpeg FFmpeg=0.8.0
FFmpeg FFmpeg=0.5.5
FFmpeg FFmpeg=0.6
FFmpeg FFmpeg=0.5.3
FFmpeg FFmpeg=0.8.10
FFmpeg FFmpeg=0.4.4
FFmpeg FFmpeg=0.5.2
FFmpeg FFmpeg<=0.9.1
FFmpeg FFmpeg=0.4.6
FFmpeg FFmpeg=0.3.4
FFmpeg FFmpeg=0.7.8
FFmpeg FFmpeg=0.4.0
FFmpeg FFmpeg=0.6.2
FFmpeg FFmpeg=0.8.7
FFmpeg FFmpeg=0.7.9
FFmpeg FFmpeg=0.5.4.5
FFmpeg FFmpeg=0.7
FFmpeg FFmpeg=0.7.12
FFmpeg FFmpeg=0.8.1
FFmpeg FFmpeg=0.4.8
FFmpeg FFmpeg=0.4.3
FFmpeg FFmpeg=0.6.3
FFmpeg FFmpeg=0.8.11
FFmpeg FFmpeg=0.8.8
FFmpeg FFmpeg=0.8.2
FFmpeg FFmpeg=0.7.11
FFmpeg FFmpeg=0.7.2
Remediation
Event History
Dec 9, 2013
CVE Published
via MITRE·11:00 AM
Data Sourced
via MITRE·11:00 AM
Description
Frequently Asked Questions
1
What is the severity of CVE-2011-3950?
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.
2
How do I fix CVE-2011-3950?
To fix CVE-2011-3950, upgrade to FFmpeg version 0.10 or later, which contains the necessary patches.
3
Which versions of FFmpeg are affected by CVE-2011-3950?
FFmpeg versions before 0.10, including 0.7.x, 0.8.x, and earlier releases, are affected by CVE-2011-3950.
4
What kind of impact can CVE-2011-3950 have?
CVE-2011-3950 can allow remote attackers to potentially execute arbitrary code on the affected system.
5
Is there a workaround for CVE-2011-3950 if I can't upgrade?
There are no known effective workarounds for CVE-2011-3950, so upgrading is strongly recommended.