Local privilege escalation via stale overlay visibility
Published Jul 9, 2024 · Updated Mar 15, 2025
Tapjacking protection bypass in Android 12, 12L, 13, and 14 allows local users to escalate privileges through screen rotation. WindowState.hide incorrectly waits for a parent container's animation callback when the window has no hide animation, leaving a policy-hidden window visible. Exploitation requires user execution privileges, a portrait-first activity rotated to landscape, and user interaction; successful tapjacking bypasses overlay protection to elevate privileges.
Summary
What happened
Tapjacking protection bypass in Android 12, 12L, 13, and 14 allows local users to escalate privileges through screen rotation. WindowState.hide incorrectly waits for a parent container's animation callback when the window has no hide animation, leaving a policy-hidden window visible. Exploitation requires user execution privileges, a portrait-first activity rotated to landscape, and user interaction; successful tapjacking bypasses overlay protection to elevate privileges.
The record
- CVE
- CVE-2024-31324
- Published
- Jul 9, 2024
- Updated
- Mar 15, 2025
- Vendor
- Product
- Android
- Classifications
- CWE-1021, T1626
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 9, 2024CVE publishedPublication date reported by the CVE source.
- Mar 15, 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=12
- Affected versionversion=12l
- Affected versionversion=12L
- Affected versionversion=13
- 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.
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