First published: Sat Dec 07 2013(Updated: )
The ff_id3v2_parse function in libavformat/id3v2.c in FFmpeg before 1.1 allows remote attackers to have an unspecified impact via ID3v2 header data, which triggers an out-of-bounds array access.
Credit: cve-coordination@google.com
Affected Software | Affected Version | How to fix |
---|---|---|
FFmpeg | <=1.0 | |
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-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 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2013-0847 is classified as having medium severity due to its potential for triggering out-of-bounds array access and allowing remote attackers to compromise the system.
To fix CVE-2013-0847, upgrade to FFmpeg version 1.1 or later, where the vulnerability has been addressed.
CVE-2013-0847 affects all FFmpeg versions before 1.1, including versions 0.3 to 1.0.
CVE-2013-0847 is associated with remote code execution attacks through crafted ID3v2 header data, potentially leading to arbitrary code execution.
As of now, there are no widely known public exploits specifically targeting CVE-2013-0847.