CVE-2013-0845: Buffer Overflow
Published Dec 7, 2013
·Updated
libavcodec/alsdec.c in FFmpeg before 1.0.4 allows remote attackers to have an unspecified impact via a crafted block length, which triggers an out-of-bounds write.
Affected Software
57 affected components
FFmpeg FFmpeg<=1.0.3
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.4.9-pre1
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.1
FFmpeg FFmpeg=1.0.2
Remediation
Event History
Dec 7, 2013
CVE Published
via MITRE·09:00 PM
Data Sourced
via MITRE·09:00 PM
Description
Frequently Asked Questions
1
What is the severity of CVE-2013-0845?
CVE-2013-0845 has been classified with a moderate severity due to the potential for remote attackers to cause an out-of-bounds write.
2
How do I fix CVE-2013-0845?
To fix CVE-2013-0845, update FFmpeg to version 1.0.4 or later.
3
Which versions of FFmpeg are affected by CVE-2013-0845?
CVE-2013-0845 affects FFmpeg versions before 1.0.4, including all 0.x versions.
4
What impact can CVE-2013-0845 have on my system?
CVE-2013-0845 can lead to undefined behavior, potentially crashing the application or allowing remote code execution.
5
Is there a workaround for CVE-2013-0845 if I cannot update FFmpeg?
While no official workaround exists, avoiding untrusted media inputs can help mitigate risks associated with CVE-2013-0845.