FFmpeg 4.1 libavcodec/cbs_av1.c array index

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

A vulnerability was found in FFmpeg 4.1 (Multimedia Processing Software). It has been declared as problematic. Affected by this vulnerability is an unknown code block of the file libavcodec/cbs_av1.c. The manipulation with an unknown input leads to a array index vulnerability. The CWE definition for the vulnerability is CWE-129. The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array. As an impact it is known to affect availability. The summary by CVE is:

FFMPEG version 4.1 contains a CWE-129: Improper Validation of Array Index vulnerability in libavcodec/cbs_av1.c that can result in Denial of service. This attack appears to be exploitable via specially crafted AV1 file has to be provided as input. This vulnerability appears to have been fixed in after commit b97a4b658814b2de8b9f2a3bce491c002d34de31.

The bug was discovered 12/02/2018. The weakness was released 02/04/2019. This vulnerability is known as CVE-2019-1000016 since 02/04/2019. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit.

The vulnerability was handled as a non-public zero-day exploit for at least 64 days. During that time the estimated underground price was around $0-$5k.

Applying the patch b97a4b658814b2de8b9f2a3bce491c002d34de31 is able to eliminate this problem.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv3info

VulDB Meta Base Score: 5.4
VulDB Meta Temp Score: 5.3

VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 6.5
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock

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

NVD Base Score: 🔍

Exploitinginfo

Class: Array index
CWE: CWE-129 / CWE-119
ATT&CK: Unknown

Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-Dayunlockunlockunlockunlock
Todayunlockunlockunlockunlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Patch
Status: 🔍

0-Day Time: 🔍

Patch: b97a4b658814b2de8b9f2a3bce491c002d34de31

Timelineinfo

12/02/2018 🔍
02/04/2019 +64 days 🔍
02/04/2019 +0 days 🔍
02/05/2019 +1 days 🔍
07/04/2023 +1610 days 🔍

Sourcesinfo

Product: ffmpeg.org

Advisory: b97a4b658814b2de8b9f2a3bce491c002d34de31
Status: Not defined

CVE: CVE-2019-1000016 (🔍)

Entryinfo

Created: 02/05/2019 09:00 AM
Updated: 07/04/2023 06:06 PM
Changes: 02/05/2019 09:00 AM (55), 05/29/2020 02:57 PM (1), 07/04/2023 06:06 PM (6)
Complete: 🔍

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!