VDB-9467 · OSVDB 95037 · GCVE-100-9467

FFmpeg up to 1.2 libavcodec/ansi.c execute_code Local Privilege Escalation

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

Summaryinfo

A vulnerability has been found in FFmpeg up to 1.2 and classified as problematic. The impacted element is the function execute_code of the file libavcodec/ansi.c. The manipulation leads to an unknown weakness. No exploit exists. To fix this issue, it is recommended to deploy a patch.

Detailsinfo

A vulnerability was found in FFmpeg up to 1.2 (Multimedia Processing Software). It has been rated as problematic. This issue affects the function execute_code of the file libavcodec/ansi.c. The impact remains unknown.

The weakness was disclosed 05/02/2013 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as confirmed git commit (GIT Repository). It is possible to read the advisory at git.videolan.org. The public release has been coordinated in cooperation with the project team. Technical details of the vulnerability are known, but there is no available exploit.

Applying a patch is able to eliminate this problem. The bugfix is ready for download at git.videolan.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 (95037†). The entries VDB-9471, VDB-9470, VDB-9469 and VDB-9468 are pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

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: 5.3
VulDB Meta Temp Score: 5.1

VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Local Privilege Escalation
CWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

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.videolan.org

Timelineinfo

05/02/2013 🔍
05/02/2013 +0 days 🔍
07/12/2013 +71 days 🔍
05/07/2018 +1760 days 🔍

Sourcesinfo

Product: ffmpeg.org

Advisory: git.videolan.org
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Confirmed
Coordinated: 🔍

GCVE (VulDB): GCVE-100-9467
OSVDB: 95037

See also: 🔍

Entryinfo

Created: 07/12/2013 12:43
Updated: 05/07/2018 08:58
Changes: 07/12/2013 12:43 (47), 05/07/2018 08:58 (1)
Complete: 🔍
Committer:
Cache ID: 216:92C:103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!