Google Android 10.0/11.0/12.0/13.0 NotificationChannel.java NotificationChannel resource consumption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.2 | $0-$5k | 2.28 |
Summary
A vulnerability was found in Google Android 10.0/11.0/12.0/13.0. It has been declared as problematic. Affected by this vulnerability is the function NotificationChannel of the file NotificationChannel.java. Executing a manipulation can lead to resource consumption.
This vulnerability appears as CVE-2022-20487. The attack requires local access. There is no available exploit.
A patch should be applied to remediate this issue.
Details
A vulnerability classified as problematic was found in Google Android 10.0/11.0/12.0/13.0 (Smartphone Operating System). This vulnerability affects the function NotificationChannel of the file NotificationChannel.java. The manipulation with an unknown input leads to a resource consumption vulnerability. The CWE definition for the vulnerability is CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. As an impact it is known to affect availability. CVE summarizes:
In NotificationChannel of NotificationChannel.java, there is a possible failure to persist permissions settings due to resource exhaustion. 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-242703202
The weakness was presented 12/13/2022 as A-242703202. The advisory is available at source.android.com. This vulnerability was named CVE-2022-20487 since 10/14/2021. Technical details are known, but there is no available exploit.
Applying a patch is able to eliminate this problem.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2022-25747). If you want to get best quality of vulnerability data, you may have to visit 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: 3.3VulDB Meta Temp Score: 3.2
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
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: Resource consumptionCWE: CWE-400 / CWE-404
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 🔍12/13/2022 🔍
12/13/2022 🔍
04/17/2026 🔍
Sources
Vendor: google.comAdvisory: A-242703202
Status: Confirmed
CVE: CVE-2022-20487 (🔍)
GCVE (CVE): GCVE-0-2022-20487
GCVE (VulDB): GCVE-100-215578
EUVD: 🔍
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 12/13/2022 22:08Updated: 04/17/2026 00:36
Changes: 12/13/2022 22:08 (43), 04/17/2026 00:36 (16)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.