VDB-10279 · OSVDB 97323 · GCVE-100-10279

FFmpeg 2.0 Video File libavcodec/shorten.c decode_wave_header privileges management

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

Summaryinfo

A vulnerability has been found in FFmpeg 2.0 and classified as problematic. Impacted is the function decode_wave_header of the file libavcodec/shorten.c of the component Video File Handler. This manipulation causes privileges management. Furthermore, there is an exploit available. It is recommended to apply a patch to fix this issue.

Detailsinfo

A vulnerability classified as problematic was found in FFmpeg 2.0 (Multimedia Processing Software). Affected by this vulnerability is the function decode_wave_header of the file libavcodec/shorten.c of the component Video File Handler. The manipulation with an unknown input leads to a privileges management vulnerability. The CWE definition for the vulnerability is CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. As an impact it is known to affect confidentiality, and integrity.

The issue has been introduced in 07/11/2013. The weakness was shared 09/12/2013 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as shorten: Use a checked bytestream reader for the wave header as confirmed git commit (GIT Repository). It is possible to read the advisory at git.libav.org. The vendor cooperated in the coordination of the public release. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a private exploit are known. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.

A private exploit has been developed by Mateusz "j00ru" Jurczyk/Gynvael Coldwind. The vulnerability was handled as a non-public zero-day exploit for at least 63 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. Currently, there are no known workarounds or upgrades to correct this issue. However, a patch has been committed to the source code repository (e.g. GIT, CVS, SVN) that addresses this vulnerability. Until it is incorporated into the next release of the software, manually patching an existing installation is the only known available solution. Check the vendor links in the references section for more information.

The vulnerability is also documented in the vulnerability database at OSVDB (97323†). Additional details are provided at git.libav.org. The entries VDB-10278, VDB-10277, VDB-10276 and VDB-10275 are related to this item. Be aware that VulDB is the high quality source for vulnerability data.

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: 4.8
VulDB Meta Temp Score: 4.2

VulDB Base Score: 4.8
VulDB Temp Score: 4.2
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Privileges management
CWE: CWE-269 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Access: Private
Status: Unproven
Author: Mateusz "j00ru" Jurczyk/Gynvael Coldwind
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/12/2013 +63 days 🔍
09/12/2013 +0 days 🔍
09/16/2013 +4 days 🔍
04/15/2019 +2037 days 🔍

Sourcesinfo

Product: ffmpeg.org

Advisory: shorten: Use a checked bytestream reader for the wave header
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Confirmed
Coordinated: 🔍

GCVE (VulDB): GCVE-100-10279
OSVDB: 97323

Misc.: 🔍
See also: 🔍

Entryinfo

Created: 09/16/2013 10:14
Updated: 04/15/2019 20:51
Changes: 09/16/2013 10:14 (57), 04/15/2019 20:51 (2)
Complete: 🔍
Cache ID: 216:5F6:103

Be aware that VulDB is the high quality source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!