Reboot-time denial of service via mis-tagged policies
Published Mar 11, 2024 · Updated Mar 27, 2025
Incorrect device-policy serialization in Google Android 14 allows local users to interrupt service availability during reboot. UserManagerService.writeUserLP writes device-policy user restrictions under the wrong XML tag, causing reboot-time deserialization to interpret them as base restrictions. Exploitation requires local low-privileged access and a subsequent reboot; the resulting failure disrupts device availability without reported confidentiality or integrity impact.
Summary
What happened
Incorrect device-policy serialization in Google Android 14 allows local users to interrupt service availability during reboot. UserManagerService.writeUserLP writes device-policy user restrictions under the wrong XML tag, causing reboot-time deserialization to interpret them as base restrictions. Exploitation requires local low-privileged access and a subsequent reboot; the resulting failure disrupts device availability without reported confidentiality or integrity impact.
The record
- CVE
- CVE-2024-0047
- Published
- Mar 11, 2024
- Updated
- Mar 27, 2025
- Vendor
- Product
- Android
- Classifications
- CWE-502, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 11, 2024CVE publishedPublication date reported by the CVE source.
- Mar 27, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=14
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo