Google Android 9.0/10.0/11.0 App Pinning LockTaskController.java shouldLockKeyguard improper authentication
|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.
A vulnerability classified as critical has been found in Google Android 9.0/10.0/11.0 (Smartphone Operating System). Affected is the function
shouldLockKeyguard of the file LockTaskController.java of the component App Pinning. The manipulation with an unknown input leads to a weak authentication vulnerability. CWE is classifying the issue as CWE-287. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
In shouldLockKeyguard of LockTaskController.java, there is a possible way to exit App Pinning without a PIN due to a permissions bypass. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11 Android-9 Android-10Android ID: A-176801033
The weakness was disclosed 06/12/2021 as A-176801033. The advisory is shared for download at source.android.com. This vulnerability is traded as CVE-2021-0472 since 11/06/2020. The exploitability is told to be easy. The attack needs to be approached locally. The exploitation doesn't require any form of authentication. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 06/18/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.
CVSSv3VulDB Meta Base Score: 6.0
VulDB Meta Temp Score: 5.8
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔒
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
NVD Base Score: 🔒
ExploitingClass: Weak authentication
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
Threat IntelligenceInterest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
0-Day Time: 🔒
Timeline11/06/2020 CVE assigned
06/12/2021 +217 days Advisory disclosed
06/12/2021 +0 days VulDB entry created
06/18/2021 +6 days VulDB last update
CVE: CVE-2021-0472 (🔒)
scip Labs: https://www.scip.ch/en/?labs.20150917
EntryCreated: 06/12/2021 11:39 AM
Updated: 06/18/2021 08:33 AM
Changes: (18) vulnerability_cvss3_nvd_av vulnerability_cvss3_nvd_ac vulnerability_cvss3_nvd_pr vulnerability_cvss3_nvd_ui vulnerability_cvss3_nvd_s vulnerability_cvss3_nvd_c vulnerability_cvss3_nvd_i vulnerability_cvss3_nvd_a vulnerability_cvss2_nvd_av vulnerability_cvss2_nvd_ac vulnerability_cvss2_nvd_au vulnerability_cvss2_nvd_ci vulnerability_cvss2_nvd_ii vulnerability_cvss2_nvd_ai vulnerability_cvss3_meta_basescore vulnerability_cvss3_meta_tempscore vulnerability_cvss2_nvd_basescore vulnerability_cvss3_nvd_basescore