Google Android 10.0/11.0/12.0/13.0 LocaleListCache.cpp toLanguageTag out-of-bounds
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.9 | $5k-$25k | 0.00 |
Summary
A vulnerability was found in Google Android 10.0/11.0/12.0/13.0. It has been classified as problematic. The impacted element is the function toLanguageTag of the file LocaleListCache.cpp. This manipulation causes out-of-bounds.
This vulnerability appears as CVE-2022-20473. The attack may be initiated remotely. There is no available exploit.
To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability has been found in Google Android 10.0/11.0/12.0/13.0 (Smartphone Operating System) and classified as critical. Affected by this vulnerability is the function toLanguageTag of the file LocaleListCache.cpp. The manipulation with an unknown input leads to a out-of-bounds vulnerability. The CWE definition for the vulnerability is CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
In toLanguageTag of LocaleListCache.cpp, there is a possible out of bounds read due to an incorrect bounds check. This could lead to remote code execution 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-239267173
The weakness was presented 12/13/2022 as A-239267173. It is possible to read the advisory at source.android.com. This vulnerability is known as CVE-2022-20473 since 10/14/2021. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 01/08/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.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
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: 8.0VulDB Meta Temp Score: 7.9
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
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: Out-of-boundsCWE: CWE-125 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
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 🔍
01/08/2023 🔍
Sources
Vendor: google.comAdvisory: A-239267173
Status: Confirmed
CVE: CVE-2022-20473 (🔍)
GCVE (CVE): GCVE-0-2022-20473
GCVE (VulDB): GCVE-100-215563
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 12/13/2022 21:06Updated: 01/08/2023 13:11
Changes: 12/13/2022 21:06 (43), 01/08/2023 13:11 (11)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.