Nils Ole Tippenhauer

**Name of the Vulnerable Software and Affected Versions** Bluetooth BR/EDR Core Specification versions prior to v5.2 **Description** The issue concerns a flaw in the authentication procedure of the Bluetooth BR/EDR protocol, allowing an unauthenticated, adjacent attacker to impersonate a Bluetooth BR/EDR master or slave and pair with a previously paired remote device without knowing the link key. This could potentially compromise the confidentiality and integrity of protected information. **Recommendations** For Bluetooth BR/EDR Core Specification versions prior to v5.2, consider implementing additional authentication measures or restricting access to sensitive data until a patch or update is available. As a temporary workaround, restrict the use of legacy pairing and secure-connections pairing authentication to minimize the risk of exploitation. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Bluetooth BR/EDR versions up to and including 5.1 **Description** The issue concerns the Bluetooth BR/EDR specification, which permits sufficiently low encryption key length and does not prevent an attacker from influencing the key length negotiation. This allows practical brute-force attacks that can decrypt traffic and inject arbitrary ciphertext without the victim noticing. The vulnerability can be exploited by an unauthenticated, adjacent attacker to initiate a man-in-the-middle attack, reducing the negotiated entropy length used for secure connections. The flaw affects a wide range of Bluetooth-enabled devices, including smartphones, laptops, IoT devices, and industrial devices. **Recommendations** For Bluetooth BR/EDR versions up to and including 5.1, consider disabling the key negotiation process until a patch is available. As a temporary workaround, restrict access to the encryption key negotiation process to minimize the risk of exploitation. Avoid using the Bluetooth BR/EDR protocol for sensitive connections until the issue is resolved. At the moment, there is no information about a newer version that contains a fix for this vulnerability.