Persistent reboot loop via illegal intent filters
Published Mar 24, 2023 · Updated Feb 25, 2025
Improper input validation in Android 13 Framework allows local users to trigger a persistent device reboot loop through an app. PackageManager intent-filter handling accepts and persists illegal PatternMatcher-backed filters instead of rejecting them. User-level app execution is sufficient, no interaction is required, and the crafted installed app leaves the device repeatedly rebooting.
Summary
What happened
Improper input validation in Android 13 Framework allows local users to trigger a persistent device reboot loop through an app. PackageManager intent-filter handling accepts and persists illegal PatternMatcher-backed filters instead of rejecting them. User-level app execution is sufficient, no interaction is required, and the crafted installed app leaves the device repeatedly rebooting.
The record
- CVE
- CVE-2023-20999
- Published
- Mar 24, 2023
- Updated
- Feb 25, 2025
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-835, T1529
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 24, 2023CVE publishedPublication date reported by the CVE source.
- Feb 25, 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=Android-13
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.
Weakness, pattern, technique
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