Google Android callreqdata.cpp CallDialReqData::encode out-of-bounds write
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Google Android. This issue affects the function CallDialReqData::encode of the file callreqdata.cpp. The manipulation leads to out-of-bounds write.
This vulnerability is uniquely identified as CVE-2022-42509. Local access is required to approach this attack. No exploit exists.
Applying a patch is the recommended action to fix this issue.
Details
A vulnerability was found in Google Android (Smartphone Operating System) (affected version unknown) and classified as critical. This issue affects the function CallDialReqData::encode of the file callreqdata.cpp. The manipulation with an unknown input leads to a out-of-bounds write vulnerability. Using CWE to declare the problem leads to CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
In CallDialReqData::encode of callreqdata.cpp, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-241544307References: N/A
The weakness was disclosed 12/16/2022 as A-241544307. The advisory is shared at source.android.com. The identification of this vulnerability is CVE-2022-42509 since 10/07/2022. 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 04/18/2025). 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
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 4.2
VulDB Temp Score: 4.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.7
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-bounds writeCWE: CWE-787 / 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/07/2022 🔍12/16/2022 🔍
12/16/2022 🔍
04/18/2025 🔍
Sources
Vendor: google.comAdvisory: A-241544307
Status: Confirmed
CVE: CVE-2022-42509 (🔍)
GCVE (CVE): GCVE-0-2022-42509
GCVE (VulDB): GCVE-100-216077
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 12/16/2022 21:33Updated: 04/18/2025 23:55
Changes: 12/16/2022 21:33 (42), 01/14/2023 09:21 (11), 04/18/2025 23:55 (16)
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.