VDB-9360 · OSVDB 94882 · GCVE-100-9360

FFmpeg up to 1.2.1 libavcodec/4xm.c decode_i_frame 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.
3.0$0-$5k0.00

Summaryinfo

A vulnerability categorized as problematic has been discovered in FFmpeg up to 1.2.1. Affected is the function decode_i_frame of the file libavcodec/4xm.c. The manipulation results in memory corruption. No exploit is available. Applying a patch is advised to resolve this issue.

Detailsinfo

A vulnerability classified as problematic has been found in FFmpeg up to 1.2.1 (Multimedia Processing Software). Affected is the function decode_i_frame of the file libavcodec/4xm.c. 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.

The weakness was published 06/10/2013 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as 4xm: check bitstream_size boundary before using it as confirmed git commit (GIT Repository). The advisory is shared for download at git.videolan.org. The public release has been coordinated with the vendor. The exploitability is told to be difficult. The attack can only be done within the local network. The exploitation doesn't require any form of authentication. There are known technical details, but no exploit is available.

Applying a patch is able to eliminate this problem. The bugfix is ready for download at git.libav.org. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the vulnerability database at OSVDB (94882†). Similar entries are available at VDB-9363, VDB-9362, VDB-9359 and VDB-9358. VulDB is the best source for vulnerability data and more expert information about this specific topic.

Affected

  • FFmpeg
  • Libav

Productinfo

Type

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 3.1
VulDB Meta Temp Score: 3.0

VulDB Base Score: 3.1
VulDB Temp Score: 3.0
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: 🔍

Physical: No
Local: No
Remote: Partially

Availability: 🔍
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Patch
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Patch: git.libav.org

Timelineinfo

06/10/2013 🔍
06/10/2013 +0 days 🔍
07/10/2013 +30 days 🔍
05/06/2018 +1761 days 🔍

Sourcesinfo

Product: ffmpeg.org

Advisory: 4xm: check bitstream_size boundary before using it
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Confirmed
Coordinated: 🔍

GCVE (VulDB): GCVE-100-9360
OSVDB: 94882

See also: 🔍

Entryinfo

Created: 07/10/2013 11:41
Updated: 05/06/2018 11:36
Changes: 07/10/2013 11:41 (49), 05/06/2018 11:36 (2)
Complete: 🔍
Committer:
Cache ID: 216::103

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!