Local privilege escalation via App Pinning bypass
Published Jun 11, 2021 · Updated Aug 3, 2024
Incorrect authorization in Android 9 through 11 allows local users to exit App Pinning without a PIN or user interaction. The shouldLockKeyguard method queries isSecure with USER_CURRENT instead of the supplied userId, so it evaluates the wrong user's lock state. An attacker needs local low-privileged app access; successful exploitation bypasses the pinning exit gate and gains additional privileges.
Summary
What happened
Incorrect authorization in Android 9 through 11 allows local users to exit App Pinning without a PIN or user interaction. The shouldLockKeyguard method queries isSecure with USER_CURRENT instead of the supplied userId, so it evaluates the wrong user's lock state. An attacker needs local low-privileged app access; successful exploitation bypasses the pinning exit gate and gains additional privileges.
The record
- CVE
- CVE-2021-0472
- Published
- Jun 11, 2021
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-863, T1404
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 11, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=Android-11 Android-9 Android-10
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