Google Android vendor_graphicbuffer_meta.cpp init use after free

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

Summaryinfo

A vulnerability identified as critical has been detected in Google Android. This issue affects the function init of the file vendor_graphicbuffer_meta.cpp. The manipulation leads to use after free. This vulnerability is referenced as CVE-2021-39679. The attack can only be performed from a local environment. No exploit is available. It is recommended to apply a patch to fix this issue.

Detailsinfo

A vulnerability was found in Google Android (Smartphone Operating System) (affected version not known) and classified as critical. This issue affects the function init of the file vendor_graphicbuffer_meta.cpp. The manipulation with an unknown input leads to a use after free vulnerability. Using CWE to declare the problem leads to CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. Impacted is confidentiality, integrity, and availability.

The weakness was published 01/15/2022 as A-188745089. It is possible to read the advisory at source.android.com. The identification of this vulnerability is CVE-2021-39679 since 08/23/2021. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 01/15/2022). 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.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 5.1

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

CVSSv2info

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

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

Exploitinginfo

Class: Use after free
CWE: CWE-416 / 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

08/23/2021 🔍
01/15/2022 +145 days 🔍
01/15/2022 +0 days 🔍
01/19/2022 +4 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: A-188745089
Status: Confirmed

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

Entryinfo

Created: 01/15/2022 07:47
Updated: 01/19/2022 11:20
Changes: 01/15/2022 07:47 (41), 01/19/2022 11:20 (1)
Complete: 🔍
Cache ID: 216::103

Be aware that VulDB is the high quality source for 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!