==================================================================== CERT-Renater Note d'Information No. 2020/VULN281 _____________________________________________________________________ DATE : 19/05/2020 HARDWARE PLATFORM(S): Bluetooth devices supporting BR/EDR. OPERATING SYSTEM(S): Systems running Bluetooth BR/EDR implementations. ===================================================================== https://www.kb.cert.org/vuls/id/647177/ _____________________________________________________________________ Bluetooth devices supporting BR/EDR are vulnerable to impersonation attacks Vulnerability Note VU#647177 Original Release Date: 2020-05-18 | Last Revised: 2020-05-18 Overview Bluetooth Basic Rate / Enhanced Data Rate (BR/EDR) Core Configurations are used for low-power short-range communications. To establish an encrypted connection, two Bluetooth devices must pair with each other using a link key. It is possible for an unauthenticated, adjacent attacker to impersonate a previously paired/bonded device and successfully authenticate without knowing the link key. This could allow an attacker to gain full access to the paired device by performing a Bluetooth Impersonation Attack (BIAS). Description Bluetooth is a short-range wireless technology based off of a core specification that defines six different core configurations, including the Bluetooth Basic Rate / Enhanced Data Rate (BR/EDR) Core Configurations. Bluetooth BR/EDR is used for low-power short-range communications. To establish an encrypted connection, two Bluetooth devices must pair with each other using a link key. It is possible for an unauthenticated, adjacent attacker to spoof the address of a previously paired remote device to successfully complete the authentication procedure with some paired/bonded devices without knowing the link key. The Bluetooth Impersonation Attack (BIAS) can be performed in two different ways, depending on which Secure Simple Pairing method (either Legacy Secure Connections or Secure Connections) was previously used to establish a connection between two devices. If the pairing procedure was completed using the Secure Connections method, the attacker could claim to be the previously paired remote device that no longer supports secure connections, thereby downgrading the authentication security. This would allow the attacker to proceed with the BIAS method against the legacy authentication unless the device they are attacking is in Secure Connections only mode. If the attacker can either downgrade authentication or is attacking a device that does not support Secure Connections, they can perform the attack using a similar method by initiating a master-slave role switch to place itself into the master role and become the authentication initiator. If successful, they complete the authentication with the remote device. If the remote device does not then mutually authenticate with the attacker in the master role, it will result in the authentication-complete notification on both devices, even though the attacker does not possess the link key. The BIAS method is able to be performed for the following reasons: Bluetooth secure connection establishment is not encrypted and the selection of secure connections pairing method is not enforced for an already established pairing, Legacy Secure Connections secure connection establishment does not require mutual authentication, a Bluetooth device can perform a role switch any time after baseband paging, and devices who paired using Secure Connections can use Legacy Secure Connections during secure connection establishment. Impact An unauthenticated, adjacent attacker could impersonate a Bluetooth BR/EDR master or slave to pair with a previously paired remote device to successfully complete the authentication procedure without knowing the link key. The BIAS attack could be combined with the Key Negotiation of Bluetooth (KNOB) attack to "impersonate a Bluetooth device, complete authentication without possessing the link key, negotiate a session key with low entropy, establish a secure connection, and brute force the session key". An attacker could initiate a KNOB attack on encryption key strength without intervening in an ongoing pairing procedure through an injection attack. If the accompanying KNOB attack is successful, an attacker may gain full access as the remote paired device. If the KNOB attack is unsuccessful, the attacker will not be able to establish an encrypted link but may still appear authenticated to the host. Solution Bluetooth host and controller suppliers should refer to the Bluetooth SIG's statement for guidance on updating their products. Downstream vendors should refer to their suppliers for updates. Vendor Information . Apple Notified: April 06, 2020 Updated: May 14, 2020 Status Affected Vendor Statement No statement is currently available from the vendor regarding this vulnerability. Vendor Information We are not aware of further vendor information regarding this vulnerability. Bluetooth SIG Notified: December 10, 2019 Updated: May 18, 2020 Status Affected Vendor Statement No statement is currently available from the vendor regarding this vulnerability. Vendor Information We are not aware of further vendor information regarding this vulnerability. Vendor References https://www.bluetooth.com/learn-about-bluetooth/bluetooth-technology/bluetooth-security/bias-vulnerability/ Broadcom Notified: April 06, 2020 Updated: May 14, 2020 Status Affected Vendor Statement No statement is currently available from the vendor regarding this vulnerability. Vendor Information We are not aware of further vendor information regarding this vulnerability. Cypress Semiconductor Notified: April 06, 2020 Updated: May 14, 2020 Status Affected Vendor Statement No statement is currently available from the vendor regarding this vulnerability. Vendor Information We are not aware of further vendor information regarding this vulnerability. Intel Notified: April 06, 2020 Updated: May 14, 2020 Status Affected Vendor Statement No statement is currently available from the vendor regarding this vulnerability. Vendor Information We are not aware of further vendor information regarding this vulnerability. QUALCOMM Incorporated Notified: April 06, 2020 Updated: May 14, 2020 Status Affected Vendor Statement No statement is currently available from the vendor regarding this vulnerability. Vendor Information We are not aware of further vendor information regarding this vulnerability. Samsung Notified: April 06, 2020 Updated: May 14, 2020 Status Affected Vendor Statement No statement is currently available from the vendor regarding this vulnerability. Vendor Information We are not aware of further vendor information regarding this vulnerability. Check Point Notified: April 06, 2020 Updated: April 14, 2020 Statement Date: April 10, 2020 Status Not Affected Vendor Statement Not vulnerable. Vendor Information We are not aware of further vendor information regarding this vulnerability. Zyxel Notified: April 06, 2020 Updated: April 20, 2020 Statement Date: April 13, 2020 Status Not Affected Vendor Statement No statement is currently available from the vendor regarding this vulnerability. Vendor Information We are not aware of further vendor information regarding this vulnerability. A10 Networks Notified: April 06, 2020 Updated: April 06, 2020 Status Unknown Vendor Statement No statement is currently available from the vendor regarding this vulnerability. Vendor Information We are not aware of further vendor information regarding this vulnerability. CVSS Metrics Group Score Vector Base 4.8 AV:A/AC:L/Au:N/C:P/I:P/A:N Temporal 4.8 E:ND/RL:ND/RC:ND Environmental 4.8 CDP:ND/TD:ND/CR:ND/IR:ND/AR:ND References https://www.bluetooth.com/learn-about-bluetooth/bluetooth-technology/bluetooth-security/bias-vulnerability/ https://francozappa.github.io/about-bias/ https://github.com/francozappa/bias https://publications.cispa.saarland/3064/ https://www.youtube.com/watch?v=fASGU7Og5_4 https://knobattack.com/ https://www.bluetooth.com/learn-about-bluetooth/bluetooth-technology/bluetooth-security/reporting-security/ Acknowledgements Thanks to Daniele Antonioli of Singapore University of Technology and Design, Nils Ole Tippenhauer of CISPA Helmholtz Center for Information Security, and Kasper Rasmussen of the University of Oxford for reporting this vulnerability. This document was written by Madison Oliver. Other Information CVE IDs: CVE-2020-10135 Date Public: 2020-04-14 Date First Published: 2020-05-18 Date Last Updated: 2020-05-18 18:16 UTC Document Revision: 29 ========================================================= + CERT-RENATER | tel : 01-53-94-20-44 + + 23/25 Rue Daviel | fax : 01-53-94-20-41 + + 75013 Paris | email:cert@support.renater.fr + =========================================================