VDB-10413 · OSVDB 97460 · GCVE-100-10413

FFmpeg 2.0 Index ibavcodec/proresdec.c unpack_alpha Remote Code Execution

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.
5.4$0-$5k0.00

Summaryinfo

A vulnerability marked as problematic has been reported in FFmpeg 2.0. The impacted element is the function unpack_alpha of the file ibavcodec/proresdec.c of the component Index Handler. Performing a manipulation results in an unknown weakness. There is no available exploit. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability classified as problematic has been found in FFmpeg 2.0 (Multimedia Processing Software). This affects the function unpack_alpha of the file ibavcodec/proresdec.c of the component Index Handler. The impact remains unknown.

The issue has been introduced in 07/11/2013. The weakness was presented 09/16/2013 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as proresdec: Properly make sure an index doesn't run past the limit as confirmed git commit (GIT Repository). The advisory is shared at git.libav.org. The public release was coordinated in cooperation with the project team. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available.

The vulnerability was handled as a non-public zero-day exploit for at least 67 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.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 (97460†). See VDB-10417, VDB-10416, VDB-10415 and VDB-10414 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

  • FFmpeg 2.0
  • Libav 9.9

Productinfo

Type

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.6
VulDB Meta Temp Score: 5.4

VulDB Base Score: 5.6
VulDB Temp Score: 5.4
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

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

Exploitinginfo

Class: Remote Code Execution
CWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

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

07/11/2013 🔍
09/16/2013 +67 days 🔍
09/16/2013 +0 days 🔍
09/23/2013 +7 days 🔍
04/15/2019 +2030 days 🔍

Sourcesinfo

Product: ffmpeg.org

Advisory: proresdec: Properly make sure an index doesn't run past the limit
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Confirmed
Coordinated: 🔍

GCVE (VulDB): GCVE-100-10413
OSVDB: 97460

See also: 🔍

Entryinfo

Created: 09/23/2013 14:44
Updated: 04/15/2019 21:11
Changes: 09/23/2013 14:44 (52), 04/15/2019 21:11 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!