CVE-2020-10134 | Bluetooth devices supporting LE and specific BR/EDR implementations are vulnerable to method confusion attacks

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.

Published: 2020-05-19 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2020-10134 is rated Moderate Risk (42/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.66%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2020-10134

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.13% 0.66% +0.53%
2 2026-04-07 0.15% 0.13% -0.03%
3 2026-02-10 — 0.15% —

Full EPSS history (14 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2020-10134

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.3 3.1 MEDIUM
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N Click to expand
Attack vector (AV:A)
Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 2.1 4.2 [email protected]
6.3 3.1 MEDIUM
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N Click to expand
Attack vector (AV:A)
Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 2.1 4.2 [email protected]
4.3 2.0 MEDIUM
AV:A/AC:M/Au:N/C:P/I:P/A:N Click to expand
Access vector (AV:A)
Requires access to an adjacent network segment.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:N)
No availability impact.
 5.5 4.9 [email protected]

Weakness enumeration for CVE-2020-10134

OS Trackers for CVE-2020-10134

vendor priority summary link
redhat medium — https://access.redhat.com/security/cve/CVE-2020-10134
suse medium CVE-2020-10134 severity moderate: SUSE including 5 source package names (bluez, bluez-cups, bluez-deprecated, bluez-devel, libbluetooth3), 65 product×package rows across 33 product lines (SUSE Enterprise Storage 7, SUSE Linux Enterprise High Performance Computing 12 SP5, … (33 product lines)): Will Not Fix 65. https://www.suse.com/security/cve/CVE-2020-10134/
ubuntu medium CVE-2020-10134 medium priority: Ubuntu including 1 source packages (bluez), 17 status rows across 17 suites (bionic, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): ignored 9, deferred 6, DNE 1, needs-triage 1. https://ubuntu.com/security/CVE-2020-10134

Affected software / configurations for CVE-2020-10134

Vendor Product Version Raw CPE
bluetooth bluetooth_core <= 5.2 cpe:2.3:a:bluetooth:bluetooth_core:*:*:*:*:br:*:*:*
bluetooth bluetooth_core <= 5.2 cpe:2.3:a:bluetooth:bluetooth_core:*:*:*:*:edr:*:*:*
bluetooth bluetooth_core <= 5.2 cpe:2.3:a:bluetooth:bluetooth_core:*:*:*:*:le:*:*:*

References for CVE-2020-10134

cvelogic Threat Intelligence