CVE-2013-4263: Buffer Overflow
Published Nov 23, 2013
·Updated
libavfilter in FFmpeg before 2.0.1 has unspecified impact and remote vectors related to a crafted "plane," which triggers an out-of-bounds heap write.
Affected Software
61 affected components
FFmpeg FFmpeg<=2.0
FFmpeg FFmpeg=0.3
FFmpeg FFmpeg=0.3.1
FFmpeg FFmpeg=0.3.2
FFmpeg FFmpeg=0.3.3
FFmpeg FFmpeg=0.3.4
FFmpeg FFmpeg=0.4.0
FFmpeg FFmpeg=0.4.2
FFmpeg FFmpeg=0.4.3
FFmpeg FFmpeg=0.4.4
FFmpeg FFmpeg=0.4.5
FFmpeg FFmpeg=0.4.6
FFmpeg FFmpeg=0.4.7
FFmpeg FFmpeg=0.4.8
FFmpeg FFmpeg=0.5
FFmpeg FFmpeg=0.5.1
FFmpeg FFmpeg=0.5.2
FFmpeg FFmpeg=0.5.3
FFmpeg FFmpeg=0.5.4
FFmpeg FFmpeg=0.5.4.5
FFmpeg FFmpeg=0.5.4.6
FFmpeg FFmpeg=0.6
FFmpeg FFmpeg=0.6.1
FFmpeg FFmpeg=0.6.2
FFmpeg FFmpeg=0.6.3
FFmpeg FFmpeg=0.7
FFmpeg FFmpeg=0.7.1
FFmpeg FFmpeg=0.7.2
FFmpeg FFmpeg=0.7.3
FFmpeg FFmpeg=0.7.4
FFmpeg FFmpeg=0.7.5
FFmpeg FFmpeg=0.7.6
FFmpeg FFmpeg=0.7.7
FFmpeg FFmpeg=0.7.8
FFmpeg FFmpeg=0.7.9
FFmpeg FFmpeg=0.7.11
FFmpeg FFmpeg=0.7.12
FFmpeg FFmpeg=0.8.0
FFmpeg FFmpeg=0.8.1
FFmpeg FFmpeg=0.8.2
FFmpeg FFmpeg=0.8.5
FFmpeg FFmpeg=0.8.5.3
FFmpeg FFmpeg=0.8.5.4
FFmpeg FFmpeg=0.8.6
FFmpeg FFmpeg=0.8.7
FFmpeg FFmpeg=0.8.8
FFmpeg FFmpeg=0.8.10
FFmpeg FFmpeg=0.8.11
FFmpeg FFmpeg=0.9
FFmpeg FFmpeg=0.9.1
FFmpeg FFmpeg=0.10
FFmpeg FFmpeg=0.10.3
FFmpeg FFmpeg=0.10.4
FFmpeg FFmpeg=0.11
FFmpeg FFmpeg=1.0
FFmpeg FFmpeg=1.1.1
FFmpeg FFmpeg=1.1.2
FFmpeg FFmpeg=1.1.3
FFmpeg FFmpeg=1.1.4
FFmpeg FFmpeg=1.2
FFmpeg FFmpeg=1.2.1
Event History
Nov 23, 2013
CVE Published
via MITRE·05:00 PM
Data Sourced
via MITRE·05:00 PM
Description
Frequently Asked Questions
1
What is the severity of CVE-2013-4263?
CVE-2013-4263 has an unspecified severity level due to its potential for remote exploitation linked to out-of-bounds heap writes.
2
How do I fix CVE-2013-4263?
To fix CVE-2013-4263, upgrade FFmpeg to version 2.0.1 or later to ensure that the vulnerability is patched.
3
What versions of FFmpeg are affected by CVE-2013-4263?
CVE-2013-4263 affects all FFmpeg versions prior to 2.0.1, including versions 0.3 through 1.2.1.
4
Can CVE-2013-4263 be exploited remotely?
Yes, CVE-2013-4263 can potentially be exploited remotely through crafted input data targeting the libavfilter.
5
What impact does CVE-2013-4263 have?
CVE-2013-4263 may lead to arbitrary code execution due to the out-of-bounds heap write resulting from the specified vulnerability.