Google Android 10.0/11.0/12.0 Lockscreen KeyguardServiceWrapper.java race condition

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

Summaryinfo

A vulnerability described as problematic has been identified in Google Android 10.0/11.0/12.0. This impacts an unknown function of the file KeyguardServiceWrapper.java of the component Lockscreen Handler. The manipulation results in race condition. This vulnerability was named CVE-2022-20006. An attack on the physical device is feasible. There is no available exploit. It is advisable to implement a patch to correct this issue.

Detailsinfo

A vulnerability was found in Google Android 10.0/11.0/12.0 (Smartphone Operating System). It has been classified as problematic. Affected is an unknown code block of the file KeyguardServiceWrapper.java of the component Lockscreen Handler. The manipulation with an unknown input leads to a race condition vulnerability. CWE is classifying the issue as CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. This is going to have an impact on confidentiality.

The weakness was presented 05/11/2022 as A-151095871. The advisory is shared for download at source.android.com. This vulnerability is traded as CVE-2022-20006 since 10/06/2021. There are known technical details, but no exploit is available.

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: 2.0
VulDB Meta Temp Score: 1.9

VulDB Base Score: 2.0
VulDB Temp Score: 1.9
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Race condition
CWE: CWE-362
CAPEC: 🔍
ATT&CK: 🔍

Physical: Yes
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

10/06/2021 🔍
05/11/2022 +217 days 🔍
05/11/2022 +0 days 🔍
05/13/2022 +2 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: A-151095871
Status: Confirmed

CVE: CVE-2022-20006 (🔍)
GCVE (CVE): GCVE-0-2022-20006
GCVE (VulDB): GCVE-100-199428
scip Labs: https://www.scip.ch/en/?labs.20150917

Entryinfo

Created: 05/11/2022 07:26
Updated: 05/13/2022 09:48
Changes: 05/11/2022 07:26 (41), 05/13/2022 09:44 (1), 05/13/2022 09:48 (1)
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 ▸

Want to stay up to date on a daily basis?

Enable the mail alert feature now!