CVE-2024-31317
Published: 09 July 2024
Summary
CVE-2024-31317 is a high-severity Deserialization of Untrusted Data (CWE-502) vulnerability in Google Android. Its CVSS base score is 7.8 (High).
Operationally, ranked in the top 8.3% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
CVE-2024-31317 is an unsafe deserialization vulnerability present in multiple functions of ZygoteProcess.java within the Android frameworks/base component. The flaw permits code execution in the context of any app when an attacker possesses the WRITE_SECURE_SETTINGS permission, and it is tracked under CWE-502. The issue received a CVSS 3.1 base score of 7.8 reflecting local attack vector, low complexity, and high impact on confidentiality, integrity, and availability.
An attacker with existing user-level execution privileges on an affected Android device can exploit the vulnerability without user interaction to escalate privileges and run arbitrary code as any installed application. Because the flaw resides in core system code handling secure settings, the escalation occurs entirely through local means after the required permission is obtained.
The June 2024 Android security bulletin and the associated framework patch at android.googlesource.com address the issue by correcting the deserialization paths in ZygoteProcess.java. The EPSS score has remained modest, with a recorded peak of 0.0796 and a current value of 0.0703, indicating limited observed exploitation interest to date.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-29213
Vulnerability details
In multiple functions of ZygoteProcess.java, there is a possible way to achieve code execution as any app via WRITE_SECURE_SETTINGS due to unsafe deserialization. This could lead to local escalation of privilege with User execution privileges needed. User interaction is not…
more
needed for exploitation.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Penetration testing supplies malicious serialized objects, detecting unsafe deserialization and supporting corrective actions.
Evaluation of untrusted data handling (deserialization testing) reveals unsafe processing, which the required remediation process addresses.
Untrusted serialized data can be deserialized and observed inside the chamber, blocking gadget-chain exploitation outside the sandbox.
Validates or rejects untrusted serialized data before deserialization occurs.
Identifies and blocks malicious code introduced through deserialization of untrusted data at system boundaries.
Integrity verification of serialized information can detect tampering before deserialization occurs.
Provenance of associated data allows detection of untrusted sources before deserialization or processing occurs.