Google Android 12.0 RequestManageCredentials.java onCreate ui layer

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

Summaryinfo

A vulnerability classified as critical has been found in Google Android 12.0. The affected element is the function onCreate of the file RequestManageCredentials.java. This manipulation causes ui layer. This vulnerability is registered as CVE-2021-39702. The attack needs to be launched locally. No exploit is available. To fix this issue, it is recommended to deploy a patch.

Detailsinfo

A vulnerability classified as critical was found in Google Android 12.0 (Smartphone Operating System). Affected by this vulnerability is the function onCreate of the file RequestManageCredentials.java. The manipulation with an unknown input leads to a ui layer vulnerability. The CWE definition for the vulnerability is CWE-1021. The web application does not restrict or incorrectly restricts frame objects or UI layers that belong to another application or domain, which can lead to user confusion about which interface the user is interacting with. As an impact it is known to affect confidentiality, integrity, and availability.

The weakness was published 03/17/2022 as A-205150380. It is possible to read the advisory at source.android.com. This vulnerability is known as CVE-2021-39702 since 08/23/2021. 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 pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 03/17/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.

Statistical analysis made it clear that VulDB provides the best quality 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: 4.8
VulDB Meta Temp Score: 4.6

VulDB Base Score: 4.8
VulDB Temp Score: 4.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Ui layer
CWE: CWE-1021
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
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: Patch
Status: 🔍

0-Day Time: 🔍

Timelineinfo

08/23/2021 🔍
03/17/2022 +206 days 🔍
03/17/2022 +0 days 🔍
03/20/2022 +3 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: A-205150380
Status: Confirmed

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

Entryinfo

Created: 03/17/2022 08:52
Updated: 03/20/2022 08:24
Changes: 03/17/2022 08:52 (42), 03/20/2022 08:24 (1)
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 ▸

Interested in the pricing of exploits?

See the underground prices here!