FFmpeg 4.2.1 libavfilter/af_afade.c buffer overflow

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

Summaryinfo

A vulnerability was found in FFmpeg 4.2.1. It has been classified as critical. Impacted is an unknown function of the file libavfilter/af_afade.c. The manipulation leads to buffer overflow. This vulnerability is uniquely identified as CVE-2020-20893. The attack is possible to be carried out remotely. No exploit exists. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability was found in FFmpeg 4.2.1 (Multimedia Processing Software) and classified as critical. This issue affects an unknown code block of the file libavfilter/af_afade.c. The manipulation with an unknown input leads to a buffer overflow vulnerability. Using CWE to declare the problem leads to CWE-120. The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer, leading to a buffer overflow. Impacted is availability.

The weakness was disclosed 09/20/2021 as 8276. The advisory is shared at trac.ffmpeg.org. The identification of this vulnerability is CVE-2020-20893 since 08/13/2020. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.

Applying the patch e1b89c76f66343d1b495165664647317c66764bb is able to eliminate this problem. The bugfix is ready for download at git.ffmpeg.org.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.3
VulDB Meta Temp Score: 4.1

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

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Buffer overflow
CWE: CWE-120 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Patch
Status: 🔍

0-Day Time: 🔍

Patch: e1b89c76f66343d1b495165664647317c66764bb

Timelineinfo

08/13/2020 🔍
09/20/2021 +403 days 🔍
09/20/2021 +0 days 🔍
09/29/2021 +9 days 🔍

Sourcesinfo

Product: ffmpeg.org

Advisory: 8276
Status: Confirmed

CVE: CVE-2020-20893 (🔍)
GCVE (CVE): GCVE-0-2020-20893
GCVE (VulDB): GCVE-100-182957

Entryinfo

Created: 09/20/2021 21:53
Updated: 09/29/2021 10:40
Changes: 09/20/2021 21:53 (41), 09/29/2021 10:34 (7), 09/29/2021 10:40 (1)
Complete: 🔍
Cache ID: 216::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 ▸

Might our Artificial Intelligence support you?

Check our Alexa App!