AOMedia up to 2021-03-24 libaom aom_dsp/noise_model.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.
5.3$0-$5k0.00

Summaryinfo

A vulnerability was found in AOMedia up to 2021-03-24. It has been classified as critical. Affected by this vulnerability is an unknown functionality of the file aom_dsp/noise_model.c of the component libaom. The manipulation leads to buffer overflow. This vulnerability is listed as CVE-2021-30475. There is no available exploit. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in AOMedia up to 2021-03-24. It has been rated as critical. This issue affects an unknown code block of the file aom_dsp/noise_model.c of the component libaom. 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 confidentiality, integrity, and availability.

The weakness was presented 06/04/2021. It is possible to read the advisory at bugs.chromium.org. The identification of this vulnerability is CVE-2021-30475. Technical details of the vulnerability are known, but there is no available exploit.

Upgrading to version 2021-03-24 eliminates this vulnerability. A possible mitigation has been published even before and not after the disclosure of the vulnerability.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.3

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

Exploitinginfo

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

Physical: No
Local: No
Remote: Partially

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: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: AOMedia 2021-03-24

Timelineinfo

03/24/2021 🔍
04/08/2021 +14 days 🔍
06/04/2021 +57 days 🔍
06/04/2021 +0 days 🔍
06/10/2021 +6 days 🔍

Sourcesinfo

Advisory: bugs.chromium.org
Status: Confirmed

CVE: CVE-2021-30475 (🔍)
GCVE (CVE): GCVE-0-2021-30475
GCVE (VulDB): GCVE-100-176363

Entryinfo

Created: 06/04/2021 21:47
Updated: 06/10/2021 07:13
Changes: 06/04/2021 21:47 (39), 06/10/2021 07:13 (5)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!