Google Android callreqdata.cpp encodeCallNumber 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. Affected by this issue is the function CallDialReqData::encodeCallNumber
of the file callreqdata.cpp. The manipulation leads to out-of-bounds write.
This vulnerability is handled as CVE-2022-42504. It is possible to launch the attack on the local host. There is no exploit available.
It is recommended to apply a patch to fix this issue.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Details
A vulnerability classified as critical was found in Google Android (Smartphone Operating System) (the affected version is unknown). Affected by this vulnerability is the function CallDialReqData::encodeCallNumber
of the file callreqdata.cpp. The manipulation with an unknown input leads to a out-of-bounds write vulnerability. The CWE definition for the vulnerability is CWE-787. The product writes 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 CallDialReqData::encodeCallNumber of callreqdata.cpp, there is a possible out of bounds write due to an incorrect 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-241232209References: N/A
The weakness was presented 12/16/2022 as A-241232209. The advisory is shared at source.android.com. This vulnerability is known as CVE-2022-42504 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.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
License
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: 🔍
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-241232209
Status: Confirmed
CVE: CVE-2022-42504 (🔍)
GCVE (CVE): GCVE-0-2022-42504
GCVE (VulDB): GCVE-100-216073
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 12/16/2022 09:13 PMUpdated: 04/18/2025 11:55 PM
Changes: 12/16/2022 09:13 PM (42), 01/14/2023 09:11 AM (11), 04/18/2025 11:55 PM (16)
Complete: 🔍
Cache ID: 18:844:40
No comments yet. Languages: en.
Please log in to comment.