Google Android Fingerprint keymaster_ipc.cpp Local Privilege Escalation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Google Android. The affected element is an unknown function of the file keymaster_ipc.cpp of the component Fingerprint Handler. The manipulation leads to an unknown weakness. This vulnerability is documented as CVE-2022-20377. The attack needs to be performed locally. There is not any exploit available. It is suggested to install a patch to address this issue.
Details
A vulnerability, which was classified as problematic, has been found in Google Android (Smartphone Operating System) (affected version not known). This issue affects some unknown functionality of the file keymaster_ipc.cpp of the component Fingerprint Handler. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
In TBD of keymaster_ipc.cpp, there is a possible to force gatekeeper, fingerprint, and faceauth to use a known HMAC key. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-222339795References: N/A
The weakness was released 08/11/2022 as A-222339795. The advisory is shared at source.android.com. The identification of this vulnerability is CVE-2022-20377 since 10/14/2021. Technical details are known, but no exploit is available.
Applying a patch is able to eliminate this problem.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Local Privilege EscalationCWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Timeline
10/14/2021 🔍08/11/2022 🔍
08/11/2022 🔍
08/11/2022 🔍
Sources
Vendor: google.comAdvisory: A-222339795
Status: Confirmed
CVE: CVE-2022-20377 (🔍)
GCVE (CVE): GCVE-0-2022-20377
GCVE (VulDB): GCVE-100-206201
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 08/11/2022 20:43Changes: 08/11/2022 20:43 (40)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.