FFmpeg 1.0 libavcodec/h264.c decode_slice_header 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.
6.2$0-$5k0.00

Summaryinfo

A vulnerability was found in FFmpeg 1.0. It has been classified as problematic. This impacts the function decode_slice_header of the file libavcodec/h264.c. The manipulation leads to memory corruption. This vulnerability is documented as CVE-2013-0850. There is not any exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in FFmpeg 1.0 (Multimedia Processing Software). It has been rated as critical. This issue affects the function decode_slice_header of the file libavcodec/h264.c. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, and integrity. The summary by CVE is:

The decode_slice_header function in libavcodec/h264.c in FFmpeg before 1.1 allows remote attackers to have an unspecified impact via crafted H.264 data, which triggers an out-of-bounds array access.

The issue has been introduced in 09/30/2012. The weakness was released 11/18/2012 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as h264: correct ref count check and limit, fix out of array accesses. as confirmed git commit (GIT Repository). The advisory is shared at git.videolan.org. The public release was coordinated with the project team. The identification of this vulnerability is CVE-2013-0850 since 01/07/2013. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available.

The vulnerability was handled as a non-public zero-day exploit for at least 49 days. During that time the estimated underground price was around $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 70807 (Debian DSA-2793-1 : libav - several vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Debian Local Security Checks.

Upgrading to version 1.1 eliminates this vulnerability. The upgrade is hosted for download at git.videolan.org. Applying a patch is able to eliminate this problem. The bugfix is ready for download at git.videolan.org. The best possible mitigation is suggested to be upgrading to the latest version. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (70807), SecurityFocus (BID 63796†), OSVDB (94255†) and Vulnerability Center (SBV-42387†). Entries connected to this vulnerability are available at VDB-9154, VDB-9155, VDB-9158 and VDB-9159. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.5
VulDB Meta Temp Score: 6.2

VulDB Base Score: 6.5
VulDB Temp Score: 6.2
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 70807
Nessus Name: Debian DSA-2793-1 : libav - several vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍

OpenVAS ID: 892793
OpenVAS Name: Debian Security Advisory DSA 2793-1 (libav - several vulnerabilities
OpenVAS File: 🔍
OpenVAS Family: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

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

Upgrade: FFmpeg 1.1
Patch: git.videolan.org

Timelineinfo

09/30/2012 🔍
11/18/2012 +49 days 🔍
11/18/2012 +0 days 🔍
12/12/2012 +24 days 🔍
01/07/2013 +26 days 🔍
06/17/2013 +161 days 🔍
11/27/2013 +163 days 🔍
12/07/2013 +10 days 🔍
05/17/2021 +2718 days 🔍

Sourcesinfo

Product: ffmpeg.org

Advisory: h264: correct ref count check and limit, fix out of array accesses.
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Confirmed
Confirmation: 🔍
Coordinated: 🔍

CVE: CVE-2013-0850 (🔍)
GCVE (CVE): GCVE-0-2013-0850
GCVE (VulDB): GCVE-100-9161

OVAL: 🔍

SecurityFocus: 63796
OSVDB: 94255
Vulnerability Center: 42387 - Libav Before 0.8.9 Remote Unspecified Code Execution Vulnerability (CVE-2013-0850), Critical

See also: 🔍

Entryinfo

Created: 06/17/2013 10:44
Updated: 05/17/2021 07:09
Changes: 06/17/2013 10:44 (79), 05/15/2017 12:09 (2), 05/17/2021 07:09 (3)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

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!