First published: Tue May 19 2020(Updated: )
Pairing in Bluetooth® Core v5.2 and earlier may permit an unauthenticated attacker to acquire credentials with two pairing devices via adjacent access when the unauthenticated user initiates different pairing methods in each peer device and an end-user erroneously completes both pairing procedures with the MITM using the confirmation number of one peer as the passkey of the other. An adjacent, unauthenticated attacker could be able to initiate any Bluetooth operation on either attacked device exposed by the enabled Bluetooth profiles. This exposure may be limited when the user must authorize certain access explicitly, but so long as a user assumes that it is the intended remote device requesting permissions, device-local protections may be weakened.
Credit: cret@cert.org
Affected Software | Affected Version | How to fix |
---|---|---|
Bluetooth Bluetooth Core | <=5.2 | |
Bluetooth Bluetooth Core | <=5.2 | |
Bluetooth Bluetooth Core | <=5.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-10134 is a vulnerability in Bluetooth Core v5.2 and earlier that allows an unauthenticated attacker to acquire credentials through improper pairing procedures.
The vulnerability occurs when an unauthenticated user initiates different pairing methods in each peer device, and both pairing procedures are completed by the end-user, allowing the attacker to acquire credentials.
The severity of CVE-2020-10134 is medium with a CVSS score of 6.3.
Bluetooth Core v5.2 and earlier versions are affected by CVE-2020-10134.
To mitigate CVE-2020-10134, it is recommended to update to the latest version of Bluetooth Core that addresses this vulnerability.