{"@odata.context":"https://api.msrc.microsoft.com/sug/v2.0/sugodata/v2.0/en-US/$metadata#vulnerability/$entity","id":"00000000-0000-0000-0000-000004ba9d54","releaseDate":"2023-11-14T08:00:00Z","cveNumber":"CVE-2023-24023","cveTitle":"Mitre: CVE-2023-24023 Bluetooth Vulnerability","releaseNumber":"2023-Nov","vulnType":"Security Vulnerability","latestRevisionDate":"2024-01-18T08:00:00Z","description":"

Microsoft is aware of the Bluetooth Forward and Future Secrecy Attacks and Defenses (BLUFFS) vulnerability. For more information regarding the vulnerability, please see this statement from the Bluetooth SIG.

\n

To address the vulnerability, Microsoft has released a software update that enforces the use of BR/EDR Secure Connections defined encryption and authentication algorithms for Bluetooth pairings that have used BR/EDR Secure Connections. If a paired device used BR/EDR Secure Connection at some point, Windows will enforce all subsequent BR/EDR connections to use BR/EDR Secure Connections.

\n

As defined by the BR/EDR Secure Connections protocol, the new BR/EDR Secure Connections algorithms will only be used when the local system and the remote paired device both support BR/EDR Secure Connections. Connections between the local system and the remote paired device will remain vulnerable if either the local system or the remote paired device never declare support for BR/EDR Secure Connections during encryption or authentication..

\n

Additionally, it is advised to increase the minimum encryption key size as described in Windows guidance for Bluetooth key length enforcement. Increasing the minimum encryption key size does not require support for BR/EDR Secure Connections.

\n","cweList":["CWE-326: Inadequate Encryption Strength"],"cweDetailsListForSearch":[],"unformattedDescription":"Microsoft is aware of the Bluetooth Forward and Future Secrecy Attacks and Defenses (BLUFFS) vulnerability. For more information regarding the vulnerability, please see [this statement](https://www.bluetooth.com/learn-about-bluetooth/key-attributes/bluetooth-security/bluffs-vulnerability/) from the Bluetooth SIG.\n\nTo address the vulnerability, Microsoft has released a software update that enforces the use of BR/EDR Secure Connections defined encryption and authentication algorithms for Bluetooth pairings that have used BR/EDR Secure Connections. If a paired device used BR/EDR Secure Connection at some point, Windows will enforce all subsequent BR/EDR connections to use BR/EDR Secure Connections.\n\nAs defined by the BR/EDR Secure Connections protocol, the new BR/EDR Secure Connections algorithms will only be used when the local system and the remote paired device both support BR/EDR Secure Connections. Connections between the local system and the remote paired device will remain vulnerable if either the local system or the remote paired device never declare support for BR/EDR Secure Connections during encryption or authentication..\n\nAdditionally, it is advised to increase the minimum encryption key size as described in [Windows guidance for Bluetooth key length enforcement](https://support.microsoft.com/en-us/topic/windows-guidance-for-bluetooth-key-length-enforcement-1b80c5b9-ddc1-31c7-1c3e-78e07c4fe877). Increasing the minimum encryption key size does not require support for BR/EDR Secure Connections.","mitreText":"CVE-2023-24023","mitreUrl":"https://www.cve.org/CVERecord?id=CVE-2023-24023","publiclyDisclosed":"No","exploited":"No","latestSoftwareReleaseId":2,"latestSoftwareRelease":"Exploitation Less Likely","olderSoftwareReleaseId":0,"denialOfService":"N/A","tag":"Microsoft Bluetooth Driver","issuingCna":"Mitre","issuingCnaId":0,"severityId":100000001,"severity":"Important","impactId":100000008,"impact":"Spoofing","langCode":"en-US","isMariner":false,"customerActionRequired":true,"customerActionRequiredId":0,"cweDetailsList":[{"keys":["cwe","cweUrl"],"values":["CWE-326: Inadequate Encryption Strength","https://cwe.mitre.org/data/definitions/326.html"]}],"articles":[{"articleType":"FAQ","description":"

Why is the MITRE Corporation the assigning CNA (CVE Numbering Authority)?

\n

CVE-2023-24023 is regarding a vulnerability reported to the Bluetooth Special Interest Group (Bluetooth SIG). MITRE assigned this CVE number on behalf of the Bluetooth organization https://www.bluetooth.com/about-us/vision/.

\n

For more information, please see this statement from the Bluetooth SIG.

\n","ordinal":10000}],"revisions":[{"cveNumber":"CVE-2023-24023","version":1,"revisionDate":"2023-11-14T08:00:00Z","initialDate":"0001-01-01T00:00:00Z","description":"

Information published.

\n","unformattedDescription":"Information published.","notificationNeeded":false,"notificationSent":false,"sourceId":"ece9df35-016a-ee11-9363-000d3afbc7d7"},{"cveNumber":"CVE-2023-24023","version":1.1,"revisionDate":"2024-01-18T08:00:00Z","initialDate":"0001-01-01T00:00:00Z","description":"

The software update Microsoft released to address this vulnerability enforces the use of BR/EDR Secure Connections defined encryption and authentication algorithms for Bluetooth pairings that have used BR/EDR Secure Connections. For more information see the Executive Summary section. This is an informational change only.

\n","unformattedDescription":"The software update Microsoft released to address this vulnerability enforces the use of BR/EDR Secure Connections defined encryption and authentication algorithms for Bluetooth pairings that have used BR/EDR Secure Connections. For more information see the Executive Summary section. This is an informational change only.","notificationNeeded":true,"notificationSent":true,"sourceId":"ab536885-36b6-ee11-9373-000d3afbc7d7"}]}