Google Android 10.0/11.0/12.0 NotificationManagerService.java getArray information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.2 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Google Android 10.0/11.0/12.0. The affected element is the function getArray of the file NotificationManagerService.java. The manipulation leads to information disclosure.
This vulnerability is traded as CVE-2022-20011. An attack has to be approached locally. There is no exploit available.
Applying a patch is the recommended action to fix this issue.
Details
A vulnerability, which was classified as problematic, has been found in Google Android 10.0/11.0/12.0 (Smartphone Operating System). This issue affects the function getArray of the file NotificationManagerService.java. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality.
The weakness was shared 05/11/2022 as A-214999128. The advisory is shared at source.android.com. The identification of this vulnerability is CVE-2022-20011 since 10/06/2021. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
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: 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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
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/06/2021 🔍05/11/2022 🔍
05/11/2022 🔍
05/13/2022 🔍
Sources
Vendor: google.comAdvisory: A-214999128
Status: Confirmed
CVE: CVE-2022-20011 (🔍)
GCVE (CVE): GCVE-0-2022-20011
GCVE (VulDB): GCVE-100-199469
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 05/11/2022 10:01Updated: 05/13/2022 14:11
Changes: 05/11/2022 10:01 (42), 05/13/2022 14:11 (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.