Google Android ipu-core-jqs-msg-transport.c ipu_core_jqs_msg_transport_kernel_write_sync use after free
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $5k-$25k | 0.00 |
Summary
A vulnerability labeled as critical has been found in Google Android. This affects the function ipu_core_jqs_msg_transport_kernel_write_sync of the file ipu-core-jqs-msg-transport.c. Such manipulation leads to use after free.
This vulnerability is referenced as CVE-2022-20155. The attack can only be performed from a local environment. No exploit is available.
It is advisable to implement a patch to correct this issue.
Details
A vulnerability was found in Google Android (Smartphone Operating System) (the affected version unknown) and classified as critical. Affected by this issue is the function ipu_core_jqs_msg_transport_kernel_write_sync of the file ipu-core-jqs-msg-transport.c. The manipulation with an unknown input leads to a use after free vulnerability. Using CWE to declare the problem leads to CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. Impacted is confidentiality, integrity, and availability. CVE summarizes:
In ipu_core_jqs_msg_transport_kernel_write_sync of ipu-core-jqs-msg-transport.c, there is a possible use-after-free due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-176754369References: N/A
The weakness was published 06/15/2022 as A-176754369. The advisory is shared for download at source.android.com. This vulnerability is handled as CVE-2022-20155 since 10/14/2021. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 06/15/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.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
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: Use after freeCWE: CWE-416 / CWE-119
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 🔍06/15/2022 🔍
06/15/2022 🔍
06/15/2022 🔍
Sources
Vendor: google.comAdvisory: A-176754369
Status: Confirmed
CVE: CVE-2022-20155 (🔍)
GCVE (CVE): GCVE-0-2022-20155
GCVE (VulDB): GCVE-100-202100
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 06/15/2022 19:26Changes: 06/15/2022 19:26 (42)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.