CVE-2019-2102 Hardcoded credentials in Android

High 8.8 Published Updated

A proximate attacker can inject keystrokes on paired Android devices if the device uses a hardcoded Bluetooth Long Term Key from the specification.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Local or same network only
Victim action needed
Not needed
Fix
None listed

What is CVE-2019-2102?

CVE-2019-2102 is a high-severity vulnerability in Google Android, published on 7 Jun 2019. It can only be exploited from the same machine or local network, with no action from the victim.

Official 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.

Weakness: CWE-264

Which versions are affected by CVE-2019-2102?

It affects 1 product.

Products include Google Android.

How do I fix CVE-2019-2102?

No fix has been published for CVE-2019-2102 yet. Limit exposure of the affected software until one is available.

Is CVE-2019-2102 being exploited?

There is no known exploitation of CVE-2019-2102 in the wild and no public exploit code.

All Google Android vulnerabilities

Sources

Also known as GHSA-5jf8-vrfc-7fr9.

Is CVE-2019-2102 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free