CVE-2020-26555: Medium severity Google Android vulnerability
A vulnerability was found in Linux Kernel, where Bluetooth BR/EDR PIN Pairing procedure is vulnerable to an impersonation attack. When an attacker connects to a victim device using the address of the device and the victim initiates a Pairing, the attacker can reflect the encrypted nonce even without knowledge of the key.
Other sources
Bluetooth Core and Mesh Specifications could allow a remote attacker to bypass security restrictions, caused by an impersonation in the BR/EDR PIN Pairing procedure flaw. By spoofing the Bluetooth Device Address (BDADDR) of the device, an attacker could exploit this vulnerability to complete pairing with a known link key, encrypt communications with the vulnerable device, and access any profiles permitted.
— IBM
Bluetooth legacy BR/EDR PIN code pairing in Bluetooth Core Specification 1.0B through 5.2 may permit an unauthenticated nearby device to spoof the BDADDR of the peer device to complete pairing without knowledge of the PIN.
— Launchpad
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2020-26555?
CVE-2020-26555 has been assigned a high severity rating due to its potential for impersonation attacks during Bluetooth pairing.
How do I fix CVE-2020-26555?
To fix CVE-2020-26555, users should update their affected software or firmware to the latest version provided by their vendors.
Which devices are affected by CVE-2020-26555?
CVE-2020-26555 affects various devices including certain versions of Bluetooth Core Specification and specific Intel wireless firmware.
What type of attack can CVE-2020-26555 lead to?
CVE-2020-26555 can lead to impersonation attacks during the Bluetooth BR/EDR PIN Pairing procedure.
Is there a workaround for CVE-2020-26555?
Currently, the best practice is to promptly apply security updates from manufacturers to mitigate the risk associated with CVE-2020-26555.