Google Android 10.0/11.0 vpu 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.8$5k-$25k0.00

Summaryinfo

A vulnerability categorized as critical has been discovered in Google Android 10.0/11.0. Affected by this vulnerability is an unknown functionality of the component vpu. Executing a manipulation can lead to memory corruption. This vulnerability is registered as CVE-2021-0367. The attack needs to be launched locally. No exploit is available. It is advisable to implement a patch to correct this issue.

Detailsinfo

A vulnerability has been found in Google Android 10.0/11.0 (Smartphone Operating System) and classified as critical. This vulnerability affects an unknown functionality of the component vpu. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability.

The weakness was published 02/27/2021. The advisory is shared for download at corp.mediatek.com. This vulnerability was named CVE-2021-0367. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 03/05/2021). It is expected to see the exploit prices for this product increasing in the near future.

Applying a patch is able to eliminate this problem.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.1
VulDB Meta Temp Score: 7.0

VulDB Base Score: 7.8
VulDB Temp Score: 7.5
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 6.4
NVD Vector: 🔍

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: Partially
Local: Yes
Remote: No

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

Timelineinfo

11/06/2020 🔍
02/27/2021 +113 days 🔍
02/27/2021 +0 days 🔍
03/05/2021 +6 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: corp.mediatek.com
Status: Confirmed

CVE: CVE-2021-0367 (🔍)
GCVE (CVE): GCVE-0-2021-0367
GCVE (VulDB): GCVE-100-170500
scip Labs: https://www.scip.ch/en/?labs.20150917

Entryinfo

Created: 02/27/2021 08:04
Updated: 03/05/2021 19:04
Changes: 02/27/2021 08:04 (39), 03/05/2021 19:01 (5), 03/05/2021 19:04 (18)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source 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!