Skip to content
Fencer Intel
medium 6.3

CVE-2020-10134 json

Bluetooth devices supporting LE and specific BR/EDR implementations are vulnerable to method confusion attacks

published 6y ago modified 4mo ago also EUVD-2020-2597

cvss
6.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 52%
public exploits
0
none known

Summary

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.

Is CVE-2020-10134 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-10134 updated cvss 6.3

bluetooth: Method Confusion Pairing Vulnerability in LE Secure Connections and BR/EDR Secure Simple Pairing

  • Red Hat Enterprise Linux 6 bluez, bluez-alsa, bluez-cups, bluez-libs, bluez-compat, bluez-gstreamer
    affected: workaround, no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 7 bluez, bluez-cups, bluez-libs, bluez-hid2hci Red Hat Enterprise Linux 8 bluez, bluez-cups, bluez-libs, bluez-obexd, bluez-hid2hci
    affected: workaround, no fix planned “Will not fix”
  • Red Hat Enterprise Linux 9 bluez, bluez-cups, bluez-libs, bluez-obexd
    affected: workaround, no fix available

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.67% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 6.3 CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N
NVD 3.1 6.3 CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N
NVD 2.0 4.3 AV:A/AC:M/Au:N/C:P/I:P/A:N

Affected products

  • Bluetooth LE

Classification

Weakness
  • CWE-351 Insufficient Type Distinction
  • CWE-436 Interpretation Conflict

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.