Local key disclosure via unsynchronized lock state
Published Jan 11, 2021 · Updated Aug 3, 2024
Information disclosure in Android 10 and 11 allows local users to access keyguard-bound keys by winning a lock-state race. The is_device_locked and set_device_locked functions access mIsDeviceLockedForUser without synchronization, allowing an inconsistent lock state to bypass lockscreen requirements. Low-privileged local access and precise timing are required; user interaction is not required, and the documented impact is limited to protected-key disclosure.
Summary
What happened
Information disclosure in Android 10 and 11 allows local users to access keyguard-bound keys by winning a lock-state race. The is_device_locked and set_device_locked functions access mIsDeviceLockedForUser without synchronization, allowing an inconsistent lock state to bypass lockscreen requirements. Low-privileged local access and precise timing are required; user interaction is not required, and the documented impact is limited to protected-key disclosure.
The record
- CVE
- CVE-2021-0320
- Published
- Jan 11, 2021
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-362, CAPEC-29, CAPEC-26
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jan 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-10
- Affected versionversion=Android-11
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