CVE-2024-31317 Deserialization in Android

High 7.8 Published Updated

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

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

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

Which versions are affected by CVE-2024-31317?

It affects 1 product.

Products include Google Android.

How do I fix CVE-2024-31317?

Apply the vendor's patch.

Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.

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: 14 proofs of concept on GitHub.

All Google Android vulnerabilities

Sources

Also known as A-316153291, ASB-A-316153291.

Is CVE-2024-31317 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free