CVE-2020-10134 Details
Description
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.
A vulnerability in Bluetooth Core versions through 5.2 allows an adjacent, unauthenticated attacker to conduct a man-in-the-middle attack during the pairing process of two devices. This is achieved by manipulating the pairing methods used by each device, leading to a confusion that can be exploited. When the attacker successfully intercepts the pairing credentials and the user mistakenly enters a numeric comparison value as a passkey, the attacker gains the ability to initiate any Bluetooth operation on the affected devices, depending on the active Bluetooth profiles.
Users are advised to update their Bluetooth devices to the latest versions recommended by manufacturers. Bluetooth product developers should modify user interfaces or documentation to warn against entering numeric comparison values as passkeys. The Bluetooth SIG is encouraging member companies to integrate necessary patches promptly.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://kb.cert.org/vuls/id/534195/ | CVE | Third Party AdvisoryUS Government Resource |
| https://www.bluetooth.com/learn-about-bluetooth/bluetooth-technology/bluetooth-security/method-vulnerability/ | CVE | Vendor Advisory |
| https://kb.cert.org/vuls/id/534195/ | [email protected] | Third Party AdvisoryUS Government Resource |
| https://www.bluetooth.com/learn-about-bluetooth/bluetooth-technology/bluetooth-security/method-vulnerability/ | [email protected] | Vendor Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-436 | Interpretation Conflict | [email protected] |
| CWE-351 | Insufficient Type Distinction | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| bluetooth bluetooth core | <= 5.2 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Nov 21, 2024 | CVE Modified | CVE |
| May 14, 2024 | CVE Modified | [email protected] |
| May 21, 2020 | Initial Analysis | [email protected] |