Keyguard-protected data disclosure via stale lock state
Published May 14, 2020 · Updated Aug 4, 2024
Information disclosure in Android 9 and 10 allows local users to read keyguard-protected data through incorrect lock-state handling. KeyguardStateMonitor pushes keyguard showing state to keystore instead of the authoritative per-user lock state held by TrustManagerService, causing a locked work profile to be represented incorrectly. Exploitation requires code running as a local low-privilege user, needs no user interaction, and is limited to disclosure rather than data modification or service interruption.
Summary
What happened
Information disclosure in Android 9 and 10 allows local users to read keyguard-protected data through incorrect lock-state handling. KeyguardStateMonitor pushes keyguard showing state to keystore instead of the authoritative per-user lock state held by TrustManagerService, causing a locked work profile to be represented incorrectly. Exploitation requires code running as a local low-privilege user, needs no user interaction, and is limited to disclosure rather than data modification or service interruption.
The record
- CVE
- CVE-2020-0104
- Published
- May 14, 2020
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 14, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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-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