Local privilege escalation via stale process state
Published Jul 12, 2023 · Updated Nov 5, 2024
Incorrect authorization in Android 13 allows local users to retain one-time permissions after their app process terminates. The OneTimePermissionUserManager getCurrentState method queries process state through a Binder API whose filter can leave a killed process marked pending-top, so permission expiry never starts. An app with a granted one-time permission can exploit the stale state without user interaction to keep that permission indefinitely after exiting.
Summary
What happened
Incorrect authorization in Android 13 allows local users to retain one-time permissions after their app process terminates. The OneTimePermissionUserManager getCurrentState method queries process state through a Binder API whose filter can leave a killed process marked pending-top, so permission expiry never starts. An app with a granted one-time permission can exploit the stale state without user interaction to keep that permission indefinitely after exiting.
The record
- CVE
- CVE-2023-21254
- Published
- Jul 12, 2023
- Updated
- Nov 5, 2024
- Vendor
- Product
- Android
- Classifications
- CWE-863, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 12, 2023CVE publishedPublication date reported by the CVE source.
- Nov 5, 2024Record 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=13
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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