CVE-2019-2102
If a BLE device were to use this as a hardcoded LTK, it is theoretically possible for a proximate attacker to remotely inject keystrokes on a paired Android host due to improperly used crypto.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (0.33%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
In the Bluetooth Low Energy (BLE) specification, there is a provided example Long Term Key (LTK). If a BLE device were to use this as a hardcoded LTK, it is theoretically possible for a proximate attacker to remotely inject keystrokes on a paired Android host due to improperly used crypto. User interaction is not needed for exploitation. Product: Android. Versions: Android-7.0 Android-7.1.1 Android-7.1.2 Android-8.0 Android-8.1 Android-9. Android ID: A-128843052.
- CVSS 3.0
- 8.8 HIGHCVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- EPSS
- 0.33% probability · 26th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-264
- Affected
- google/android
- Source
- security@android.com
References
- https://source.android.com/security/bulletin/2019-06-01Vendor Advisory
- https://support.apple.com/kb/HT210118
- https://support.apple.com/kb/HT210119
- https://support.apple.com/kb/HT210120
- https://source.android.com/security/bulletin/2019-06-01Vendor Advisory
- https://support.apple.com/kb/HT210118
- https://support.apple.com/kb/HT210119
- https://support.apple.com/kb/HT210120
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.