FFmpeg 2.0 read_var_block_data memory corruption

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.4$0-$5k0.09

A vulnerability classified as critical has been found in FFmpeg 2.0 (Multimedia Processing Software). Affected is the function read_var_block_data. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability.

The issue has been introduced in 07/11/2013. The weakness was released 02/15/2014 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as avcodec/alsdec: check predictor order against block length as confirmed git commit (GIT Repository). The advisory is available at git.videolan.org. This vulnerability is traded as CVE-2014-125015. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details are known, but there is no available exploit.

The vulnerability was handled as a non-public zero-day exploit for at least 219 days. During that time the estimated underground price was around $0-$5k.

Applying a patch is able to eliminate this problem. The bugfix is ready for download at git.videolan.org.

The vulnerability is also documented in the vulnerability database at X-Force (91210). Entries connected to this vulnerability are available at 12365 and 12367.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB CVSS-B Score: 🔍
VulDB CVSS-BT Score: 🔍
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.3
VulDB Meta Temp Score: 6.4

VulDB Base Score: 7.3
VulDB Temp Score: 6.4
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Local: No
Remote: Yes

Availability: 🔍
Status: Unproven

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-Dayunlockunlockunlockunlock
Todayunlockunlockunlockunlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Patch
Status: 🔍

0-Day Time: 🔍

Patch: git.videolan.org

Timelineinfo

07/11/2013 🔍
02/15/2014 +219 days 🔍
02/18/2014 +3 days 🔍
02/22/2014 +4 days 🔍
06/17/2022 +3037 days 🔍

Sourcesinfo

Product: ffmpeg.org

Advisory: avcodec/alsdec: check predictor order against block length
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Confirmed

CVE: CVE-2014-125015 (🔍)
X-Force: 91210 - FFmpeg read_var_block_data() buffer overflow, Medium Risk
Secunia: 56987 - FFmpeg Multiple Vulnerabilities, Moderately Critical

See also: 🔍

Entryinfo

Created: 02/22/2014 20:06
Updated: 06/17/2022 23:30
Changes: 02/22/2014 20:06 (53), 04/17/2019 06:42 (1), 06/17/2022 23:30 (3)
Complete: 🔍

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you know our Splunk app?

Download it now for free!