Your submission was sent successfully! Close

CVE-2020-10134

Published: 19 May 2020

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.

Priority

Medium

CVSS 3 base score: 6.3

Status

Package Release Status
bluez
Launchpad, Ubuntu, Debian
bionic Deferred

eoan Ignored
(reached end-of-life)
focal Deferred

groovy Ignored
(reached end-of-life)
hirsute Ignored
(reached end-of-life)
impish Deferred

jammy Deferred

precise Does not exist

trusty Does not exist

upstream Needs triage

xenial Deferred

Notes

AuthorNote
seth-arnold
This appears to be a flaw in the protocol; it's possible that any
"fixes" for this issue may be strictly user-interface messages to the user.
mdeslaur
no software fix available as of 2021-12-08

References

Bugs