CVE-2021-0320 — Race Condition in Google Android

CWE-362 — Race Condition5 documents5 sources
Severity
4.7MEDIUMNVD
EPSS
0.0%
top 97.99%
CISA KEV
Not in KEV
Exploit
No known exploits
Affected products
2
Platform System SecurityGoogle Android
Timeline
PublishedJan 11
Latest updateMay 24

Description

In is_device_locked and set_device_locked of keystore_keymaster_enforcement.h, there is a possible bypass of lockscreen requirements for keyguard bound keys due to a race condition. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation. Product: Android; Versions: Android-10, Android-11; Android ID: A-169933423.

CVSS vector

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:NExploitability: 1.0 | Impact: 3.6

Affected Packages3 packages

▶CVEListV5google/androidAndroid-10, Android-11+1
▶NVDgoogle/android10.0, 11.0+1
▶Androidplatform/system_security10:0 — 10:2021-01-01+1

Patches

Patch: source.android.com ↗Patch: source.android.com ↗

🔴Vulnerability Details

3
GHSA
GHSA-6pfh-vwh5-gvrc: In is_device_locked and set_device_locked of keystore_keymaster_enforcement↗2022-05-24
▶
CVEList
CVE-2021-0320: In is_device_locked and set_device_locked of keystore_keymaster_enforcement↗2021-01-11
▶
OSV
CVE-2021-0320: In is_device_locked and set_device_locked of keystore_keymaster_enforcement↗2021-01-01
▶

📋Vendor Advisories

1
Android
CVE-2021-0320: Android Security Bulletin 2021-01-01 CVE: CVE-2021-0320 Severity: HIGH Type: ID Affected AOSP versions: 10, 11 References: A-169933423↗2021-01-01
▶
CVE-2021-0320 — Race Condition in Google Android | cvebase