Google Android 12.0 CarNotificationListener.java StatusBarNotification.getKey log file

CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
4.3 | $0-$5k | 0.00 |
A vulnerability was found in Google Android 12.0 (Smartphone Operating System). It has been declared as problematic. Affected by this vulnerability is the function StatusBarNotification.getKey
of the file CarNotificationListener.java. The manipulation with an unknown input leads to a log file vulnerability. The CWE definition for the vulnerability is CWE-532. Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information. As an impact it is known to affect confidentiality. The summary by CVE is:
The logs of sensitive information (PII) or hardware identifier should only be printed in Android "userdebug" or "eng" build. StatusBarNotification.getKey() could contain sensitive information. However, CarNotificationListener.java, it prints out the StatusBarNotification.getKey() directly in logs, which could contain user's account name (i.e. PII), in Android "user" build.Product: AndroidVersions: Android-12LAndroid ID: A-205567776
The weakness was released 01/27/2023 as A-205567776. It is possible to read the advisory at source.android.com. This vulnerability is known as CVE-2022-20458 since 10/14/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 02/20/2023). It is expected to see the exploit prices for this product increasing in the near future.The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.
Applying a patch is able to eliminate this problem.
Product
Type
Vendor
Name
License
- free
CPE 2.3
CPE 2.2
CVSSv3
VulDB Meta Base Score: 4.4VulDB Meta Temp Score: 4.3
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔒
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: Log fileCWE: CWE-532 / CWE-200 / CWE-284
ATT&CK: T1592
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 CVE reserved01/27/2023 Advisory disclosed
01/27/2023 VulDB entry created
02/20/2023 VulDB last update
Sources
Vendor: google.comAdvisory: A-205567776
Status: Confirmed
CVE: CVE-2022-20458 (🔒)
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 01/27/2023 09:13 AMUpdated: 02/20/2023 07:14 AM
Changes: 01/27/2023 09:13 AM (43), 02/20/2023 07:14 AM (11)
Complete: 🔍
No comments yet. Languages: en.
Please log in to comment.