FFmpeg 1.0 libavformat/id3v2.c ff_id3v2_parse memory corruption
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
6.2 | $0-$5k | 0.00 |
A vulnerability, which was classified as critical, has been found in FFmpeg 1.0 (Multimedia Processing Software). Affected by this issue is the function ff_id3v2_parse
of the file libavformat/id3v2.c. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is confidentiality, and integrity. CVE summarizes:
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.
The issue has been introduced in 09/30/2012. The weakness was shared 11/29/2012 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as id3v2: check index against buffer size. Fix out of array access as confirmed git commit (GIT Repository). The advisory is shared for download at git.videolan.org. The vendor cooperated in the coordination of the public release. This vulnerability is handled as CVE-2013-0847 since 01/07/2013. The attack may be launched remotely. No form of authentication is required for exploitation. There are known technical details, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 60 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 1.1 eliminates this vulnerability. The upgrade is hosted for download at git.videolan.org. Applying a patch is able to eliminate this problem. The bugfix is ready for download at git.videolan.org. The best possible mitigation is suggested to be upgrading to the latest version. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The entries 9168, 9167, 9166 and 9165 are related to this item.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB CVSS-B Score: 🔍VulDB CVSS-BT Score: 🔍
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.2
VulDB Base Score: 6.5
VulDB Temp Score: 6.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
AV | AC | Au | C | I | A |
---|---|---|---|---|---|
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
---|---|---|---|---|---|
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
ATT&CK: Unknown
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
0-Day | unlock | unlock | unlock | unlock |
---|---|---|---|---|
Today | unlock | unlock | unlock | unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: FFmpeg 1.1
Patch: git.videolan.org
Timeline
09/30/2012 🔍11/29/2012 🔍
11/29/2012 🔍
01/07/2013 🔍
06/17/2013 🔍
12/07/2013 🔍
04/15/2019 🔍
Sources
Product: ffmpeg.orgAdvisory: id3v2: check index against buffer size. Fix out of array access
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Confirmed
Confirmation: 🔍
Coordinated: 🔍
CVE: CVE-2013-0847 (🔍)
OSVDB: 94258
See also: 🔍
Entry
Created: 06/17/2013 10:58Updated: 04/15/2019 09:46
Changes: 06/17/2013 10:58 (64), 04/15/2019 09:46 (1)
Complete: 🔍
No comments yet. Languages: en.
Please log in to comment.