# CVE-2024-31317: Deserialization in Android

> Unsafe deserialization in Android ZygoteProcess allows local attackers to execute code and escalate privileges via WRITE_SECURE_SETTINGS.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Jul 2024
- **Updated:** 2 Aug 2024
- **Also known as:** A-316153291, ASB-A-316153291

## What is CVE-2024-31317?

CVE-2024-31317 is a high-severity unsafe deserialization vulnerability in Google Android, published on 9 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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 needed for exploitation.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2024-31317?

It affects 1 product.


Products: Google Android.

## How do I fix CVE-2024-31317?

Apply the vendor's patch.

## Is CVE-2024-31317 being exploited?

There is no known exploitation of CVE-2024-31317 in the wild and no public exploit code.

Public exploit code:

- Quick tool for utilizing CVE-2024-31317 on Android (github_poc): https://github.com/wqry085/PoC-Deployer-System
- CVE-2024-31317 (github_poc): https://github.com/fuhei/CVE-2024-31317
- A command-line utility to exploit Android Zygote injection (CVE-2024-31317) (github_poc): https://github.com/Anonymous941/zygote-injection-toolkit
- https://github.com/WebLDix/CVE-2024-31317-PoC-Deployer (github_poc): https://github.com/WebLDix/CVE-2024-31317-PoC-Deployer
- Detailed discussion of Zygote vulnerability CVE-2024-31317 (github_poc): https://github.com/agg23/cve-2024-31317
- CVE-2024-31317 Debuggable App Exploit (github_poc): https://github.com/CleoV2/Debuggable-App-Exploit

## Other vulnerabilities in Google Android

- [CVE-2026-58704](https://insights.sbomify.com/CVE-2026-58704/): Google Pixel Improper Authorization (high 8.8, exploited in the wild)
- [CVE-2025-48543](https://insights.sbomify.com/CVE-2025-48543/): Android Runtime Use-After-Free (high 8.8, exploited in the wild)
- [CVE-2023-35674](https://insights.sbomify.com/CVE-2023-35674/): Android Framework Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2025-48595](https://insights.sbomify.com/CVE-2025-48595/): Android Framework Integer Overflow (high 8.4, exploited in the wild)
- [CVE-2024-32896](https://insights.sbomify.com/CVE-2024-32896/): Android Pixel Privilege Escalation (high 8.1, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-31317 and fix it if it is affected.

What it is: CVE-2024-31317 is a high-severity unsafe deserialization vulnerability in Google Android, published on 9 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-31317 in the wild and no public exploit code.

Affected product: Google Android. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-31317/ (Markdown: https://insights.sbomify.com/CVE-2024-31317/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-31317
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-31317
- OSV: https://osv.dev/vulnerability/CVE-2024-31317

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-31317/
Summaries are generated and may contain mistakes; the official description above is the record.