Google Android 10.0/11.0/12.0/13.0 StatusBarNotificationActivityStarter.java handleFullScreentent Local Privilege Escalation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Google Android 10.0/11.0/12.0/13.0 and classified as problematic. Affected by this vulnerability is the function handleFullScreentent of the file StatusBarNotificationActivityStarter.java. This manipulation causes an unknown weakness.
This vulnerability is handled as CVE-2022-20415. It is possible to launch the attack on the local host. There is not any exploit available.
Applying a patch is the recommended action to fix this issue.
Details
A vulnerability was found in Google Android 10.0/11.0/12.0/13.0 (Smartphone Operating System). It has been declared as problematic. Affected by this vulnerability is the function handleFullScreentent of the file StatusBarNotificationActivityStarter.java. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
In handleFullScreenIntent of StatusBarNotificationActivityStarter.java, there is a possible bypass of the restriction of starting activity from background due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-10 Android-11 Android-12 Android-12L Android-13Android ID: A-231322873
The weakness was released 10/12/2022 as A-231322873. The advisory is shared at source.android.com. This vulnerability is known as CVE-2022-20415 since 10/14/2021. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 12/07/2022). 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.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
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 🔍10/12/2022 🔍
10/12/2022 🔍
12/07/2022 🔍
Sources
Vendor: google.comAdvisory: A-231322873
Status: Confirmed
CVE: CVE-2022-20415 (🔍)
GCVE (CVE): GCVE-0-2022-20415
GCVE (VulDB): GCVE-100-210661
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 10/12/2022 11:07Updated: 12/07/2022 14:54
Replaces Duplicates: 🔍
Changes: 10/12/2022 11:07 (41), 12/07/2022 14:54 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.