Blutooth BR/EDR specification does not specify sufficient encryption key length and allows an attacker to influence key length negotiation
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.6epss 2.7%
exploitation probability
2.7%top 16% of all CVEs
observed exploitation
nono source reports it
The Bluetooth BR/EDR specification up to and including version 5.1 permits sufficiently low encryption key length and does not prevent an attacker from influencing the key length negotiation. This allows practical brute-force attacks (aka "KNOB") that can decrypt traffic and inject arbitrary ciphertext without the victim noticing.
CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
Affected products
Bluetooth · BR/EDRReferences
http://lists.opensuse.org/opensuse-security-announce/2019-10/msg00036.htmlhttp://lists.opensuse.org/opensuse-security-announce/2019-10/msg00037.htmlhttps://access.redhat.com/errata/RHSA-2019:2975https://access.redhat.com/errata/RHSA-2019:3055https://access.redhat.com/errata/RHSA-2019:3076https://access.redhat.com/errata/RHSA-2019:3089https://access.redhat.com/errata/RHSA-2019:3165https://access.redhat.com/errata/RHSA-2019:3187https://access.redhat.com/errata/RHSA-2019:3217https://access.redhat.com/errata/RHSA-2019:3218https://access.redhat.com/errata/RHSA-2019:3220https://access.redhat.com/errata/RHSA-2019:3231