4.3 Medium
CVSS2
Attack Vector
ADJACENT_NETWORK
Attack Complexity
MEDIUM
Authentication
NONE
Confidentiality Impact
PARTIAL
Integrity Impact
PARTIAL
Availability Impact
NONE
AV:A/AC:M/Au:N/C:P/I:P/A:N
6.3 Medium
CVSS3
Attack Vector
ADJACENT
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
REQUIRED
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
LOW
Availability Impact
NONE
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N
0.001 Low
EPSS
Percentile
21.6%
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.
Author | Note |
---|---|
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 |
4.3 Medium
CVSS2
Attack Vector
ADJACENT_NETWORK
Attack Complexity
MEDIUM
Authentication
NONE
Confidentiality Impact
PARTIAL
Integrity Impact
PARTIAL
Availability Impact
NONE
AV:A/AC:M/Au:N/C:P/I:P/A:N
6.3 Medium
CVSS3
Attack Vector
ADJACENT
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
REQUIRED
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
LOW
Availability Impact
NONE
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N
0.001 Low
EPSS
Percentile
21.6%