VDB-9517 · SA54164 · OSVDB 95127

FFmpeg up to 2.0 libavcodec/indeo4.c decode_band_hdr 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 marked as problematic has been reported in FFmpeg up to 2.0. This affects the function decode_band_hdr of the file libavcodec/indeo4.c. This manipulation causes an unknown weakness. No exploit exists. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability has been found in FFmpeg up to 2.0 (Multimedia Processing Software) and classified as problematic. Affected by this vulnerability is the function decode_band_hdr of the file libavcodec/indeo4.c. The impact remains unknown.

The weakness was disclosed 07/13/2013 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as confirmed git commit (GIT Repository). The advisory is shared at git.videolan.org. The public release has been coordinated in cooperation with the project team. Technical details are known, 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 databases at OSVDB (95127†) and Secunia (SA54164†). The entries VDB-9516, VDB-9518 and VDB-9519 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

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

Timelineinfo

07/13/2013 🔍
07/13/2013 +0 days 🔍
07/16/2013 +3 days 🔍
07/16/2013 +0 days 🔍
05/07/2018 +1756 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-9517
Secunia: 54164 - FFmpeg Multiple Vulnerabilities, Moderately Critical
OSVDB: 95127

See also: 🔍

Entryinfo

Created: 07/16/2013 12:27
Updated: 05/07/2018 09:07
Changes: 07/16/2013 12:27 (51), 05/07/2018 09:07 (1)
Complete: 🔍
Committer:
Cache ID: 216:343: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 ▸

Want to know what is going to be exploited?

We predict KEV entries!