CVE-2020-10134

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

Configuration 1 (hide)

OR cpe:2.3:a:bluetooth:bluetooth_core:*:*:*:*:br:*:*:*
cpe:2.3:a:bluetooth:bluetooth_core:*:*:*:*:edr:*:*:*
cpe:2.3:a:bluetooth:bluetooth_core:*:*:*:*:le:*:*:*

History

No history.

Information

Published : 2020-05-19 16:15

Updated : 2024-02-28 17:47


NVD link : CVE-2020-10134

Mitre link : CVE-2020-10134

CVE.ORG link : CVE-2020-10134


JSON object : View

Products Affected

bluetooth

  • bluetooth_core
CWE
CWE-436

Interpretation Conflict

CWE-351

Insufficient Type Distinction