Google Android 12.0 CarNotificationListener.java StatusBarNotification.getKey log file
|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 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.
Applying a patch is able to eliminate this problem.
CVSSv3VulDB Meta Base Score: 4.4
VulDB 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: 🔒
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
ExploitingClass: Log file
CWE: CWE-532 / CWE-200 / CWE-284
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
Threat IntelligenceInterest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
0-Day Time: 🔒
Timeline10/14/2021 CVE reserved
01/27/2023 +470 days Advisory disclosed
01/27/2023 +0 days VulDB entry created
02/20/2023 +24 days VulDB last update
CVE: CVE-2022-20458 (🔒)
scip Labs: https://www.scip.ch/en/?labs.20150917
EntryCreated: 01/27/2023 09:13 AM
Updated: 02/20/2023 07:14 AM
Changes: 01/27/2023 09:13 AM (43), 02/20/2023 07:14 AM (11)
Interested in the pricing of exploits?
See the underground prices here!
No comments yet. Languages: en.
Please log in to comment.