Your submission was sent successfully! Close

You have successfully unsubscribed! Close


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.


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.
no software fix available as of 2021-12-08



Cvss 3 Severity Score


Score breakdown


Package Release Status
Launchpad, Ubuntu, Debian
hirsute Ignored
(end of life)
kinetic Ignored
(end of life, was deferred)
xenial Deferred

jammy Deferred

impish Ignored
(end of life)
bionic Deferred

eoan Ignored
(end of life)
focal Deferred

groovy Ignored
(end of life)
lunar Deferred

trusty Does not exist

upstream Needs triage

Severity score breakdown

Parameter Value
Base score 6.3
Attack vector Adjacent
Attack complexity Low
Privileges required None
User interaction Required
Scope Unchanged
Confidentiality High
Integrity impact Low
Availability impact None
Vector CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N