Google Android up to 15 AccountManagerService.java checkKeyIntentParceledCorrectly deserialization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $5k-$25k | 0.00 |
Summary
A vulnerability was found in Google Android 12/12L/13/14/15. It has been rated as problematic. Affected is the function checkKeyIntentParceledCorrectly of the file AccountManagerService.java. Performing a manipulation results in deserialization.
This vulnerability is cataloged as CVE-2024-49744. The attack must be initiated from a local position. There is no exploit available.
It is suggested to install a patch to address this issue.
Details
A vulnerability was found in Google Android 12/12L/13/14/15. It has been classified as problematic. This affects the function checkKeyIntentParceledCorrectly of the file AccountManagerService.java. The manipulation with an unknown input leads to a deserialization vulnerability. CWE is classifying the issue as CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
In checkKeyIntentParceledCorrectly of AccountManagerService.java, there is a possible way to bypass parcel mismatch mitigation due to unsafe deserialization. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.
The advisory is shared at source.android.com. This vulnerability is uniquely identified as CVE-2024-49744 since 10/18/2024. The exploitability is told to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 03/19/2025).
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
Version
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 7.8
CNA Vector (google_android): 🔍
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: DeserializationCWE: CWE-502 / CWE-20
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/18/2024 🔍01/22/2025 🔍
01/22/2025 🔍
03/19/2025 🔍
Sources
Vendor: google.comAdvisory: source.android.com
Status: Confirmed
CVE: CVE-2024-49744 (🔍)
GCVE (CVE): GCVE-0-2024-49744
GCVE (VulDB): GCVE-100-292929
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 01/22/2025 07:50Updated: 03/19/2025 00:08
Changes: 01/22/2025 07:50 (22), 01/22/2025 07:51 (34), 01/22/2025 16:25 (11), 03/19/2025 00:08 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.