Security Advisory

CVE-2023-24023: BLUFFS Bluetooth BR/EDR Session Key Attack

Last updated:
  • CVE-2023-24023

CVE-2023-24023, BLUFFS, is a flaw in Bluetooth BR/EDR session key setup in Core Specification 4.2 to 5.4: a nearby man in the middle forces two bonded devices into legacy encryption with a short key reused across sessions, then brute-forces it to decrypt or inject traffic. NVD scores it 6.8. LE-only devices are not affected.

Vulnerability summary

CVSS base score

6.8

Medium severity

EPSS score (FIRST)

1.3%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

No

Not listed

Published

Vulnerability ID: CVE-2023-24023 · Source: NVD

Affected components

ComponentCPEVersion range
Bluetooth Core Specification BR/EDR (Secure Simple Pairing, Secure Connections)cpe:2.3:a:bluetooth:bluetooth_core_specification:*:*:*:*:*:*:*:*4.2 through 5.4 (NVD, Bluetooth SIG notice)
Espressif ESP32 series (ESP-IDF Bluedroid, Bluetooth Classic)—all ESP-IDF releases per Espressif AR2023-010; KNOB fix (minimum 7-octet key) in maintained branches v4.3 to v5.2; BIAS fix in v4.3.5, v4.4.4, v5.0.1, v5.1
u-blox Bluetooth Classic modules (OBS421, ODIN-W2, NINA-W15, NINA-B2, NINA-W10, NINA-B50, LILY-W1, EMMY-W1, JODY-W1 to W5, MAYA-W1 to W3)—all variants affected per u-blox UBXDOC-132308279-35907; 7-octet minimum key in place except OBS421 (5 octets)
Microsoft Windows 10, Windows 11, Windows Server 2019 and 2022cpe:2.3:o:microsoft:windows_11_23h2:*:*:*:*:*:*:*:*before the November 2023 updates (e.g. Windows 11 23H2 before 10.0.22631.2715, Windows 10 22H2 before 10.0.19045.3693) per NVD CPEs
Linux kernel (Debian package linux)—Debian: fixed in 6.1.76-1 (bookworm) and 6.6.9-1 (unstable)

What does this mean for affected devices?

NVD's description: "Bluetooth BR/EDR devices with Secure Simple Pairing and Secure Connections pairing in Bluetooth Core Specification 4.2 through 5.4 allow certain man-in-the-middle attacks that force a short key length, and might lead to discovery of the encryption key and live injection, aka BLUFFS." NVD's Primary score is 6.8, CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N, with no CWE assigned; CISA's ADP entry scores it 6.4 with user interaction required, and Microsoft classes it CWE-326 (inadequate encryption strength). NVD's CPEs cover the Core Specification 4.2 through 5.4 and Windows 10, 11, Server 2019 and Server 2022 builds before the November 2023 updates (NVD).

How does BLUFFS work?

The Bluetooth SIG notice credits researchers at EURECOM. A MITM spoofs each of two already bonded devices to the other and makes both start a new encryption procedure using legacy encryption, in the Peripheral role. It can then force the minimum key length both accept and fix all nonces, so "the same encryption key is used for every session while in proximity". If the key length drops below 7 octets, the attacker can brute-force it in real time and inject traffic; once one key is broken, all sessions using it can be decrypted. The SIG says "any conforming BR/EDR implementation is expected to be vulnerable". (The SIG's notice table lists the range as Core 4.2 to 5.2, while the notice text and NVD say 4.2 through 5.4.)

Which embedded products have a vendor statement?

  • Espressif AR2023-010 (2024-01-18): only the ESP32 series is affected, since it is the line with Bluetooth Classic, regardless of ESP-IDF release. The KNOB fix, which enforces a key of at least 7 octets, is in the maintained ESP-IDF branches v4.3 to v5.2; the BIAS fix that blocks Secure Connections downgrades is in v4.3.5, v4.4.4, v5.0.1 and v5.1.
  • u-blox UBXDOC-132308279-35907 (2024-07-26): all Bluetooth Classic modules are affected, LE-only products are not. Most modules already enforce a 7-octet minimum key; the older OBS421 uses 5 octets, and u-blox recommends moving to NINA-B1 or NINA-B2.
  • Microsoft (MSRC, 2023-11-14): Windows now enforces BR/EDR Secure Connections algorithms for any peer that has used them, and Microsoft advises raising the minimum encryption key size.
  • Linux: the Debian tracker lists the kernel fixed in 6.1.76-1 (bookworm) and 6.6.9-1 (unstable).

How do you mitigate it?

The SIG advises rejecting service-level connections on links with keys under 7 octets, or under 16 octets where Security Mode 4 Level 4 is always possible. Use Secure Connections Only mode on both devices, store whether a link key came from Secure Connections, and drop the link if a later session does not use it. LE-only devices are not affected, but a dual-mode chip is. Our Bluetooth LE security guide explains which flaws apply to dual-mode parts, and the weak cryptography fix guide covers short keys. CVE-2019-9506 (KNOB) is the older key-length attack BLUFFS builds on, and CVE-2022-25836 is the LE pairing equivalent.

CVE-2023-24023 is not in the CISA KEV catalog as of 2026-11-18 (catalog version 2026.11.17). FIRST EPSS gives it 0.0134, the 71.7th percentile, in the 2026-11-17 dataset (CISA KEV, FIRST EPSS).

How to fix this class of issueNo dedicated SoftWSP guide covers this weakness class; the fix is usually the vendor patch or firmware update referenced above. Our related guide explains how to plan and verify it: NIST SP 800-40 Rev. 4: enterprise patch management planning, explained.

Evidence

  • BR/EDR with SSP and Secure Connections in Core 4.2 through 5.4 allow MITM forcing short key length, BLUFFS; NVD Primary 6.8 AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N; NVD-CWE-noinfo; CISA-ADP 6.4 AV:A/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N; CPEs core spec 4.2-5.4 and Windows 10/11/Server 2019/2022 builds (e.g. windows_11_23h2 before 10.0.22631.2715, windows_10_22h2 before 10.0.19045.3693); published 2023-11-28. — NVD
  • Researchers at EURECOM; BR/EDR SC and SSP in Core 4.2 through 5.4; MITM forces legacy encryption and Peripheral role, minimum key length and fixed nonces; same key every session; any conforming BR/EDR implementation expected vulnerable; below 7 octets real-time brute force and live injection; mitigations: reject keys under 7 octets (16 with Security Mode 4 Level 4), Secure Connections Only Mode, track SC link keys and terminate otherwise. SIG notices table lists BLUFFS 27/11/2023, Core Spec v4.2 to 5.2. — Bluetooth SIG
  • MSRC CVE-2023-24023, release 2023-11-14 (2023-Nov), revised 2024-01-18; Windows enforces BR/EDR Secure Connections algorithms for pairings that used them; advises increasing minimum encryption key size; CWE-326. — Microsoft MSRC
  • Espressif AR2023-010, 2024/01/18: only ESP32 series affected, regardless of ESP-IDF release; KNOB fix (min 7 octets) in maintained branches v4.3 to v5.2; BIAS fix in v5.1, v5.0.1, v4.4.4, v4.3.5. — Espressif
  • u-blox advisory dated 26 July 2024: affects all products with Bluetooth Classic, LE products not affected; OBS421 minimum key length 5 octets, recommend upgrade to NINA-B1 or NINA-B2; ODIN-W2, NINA-W15, NINA-B2, NINA-W10, NINA-B50, LILY-W1, EMMY-W1, JODY-W1 to W5, MAYA-W1 to W3 mitigation in place with 7 octets. — u-blox
  • Debian linux fixed in bookworm 6.1.76-1 and unstable 6.6.9-1. — Debian security tracker
  • Not in the CISA KEV catalog, version 2026.11.17 (1,782 entries), checked 2026-11-18. — CISA KEV
  • EPSS 0.01336, percentile 0.71719, dataset 2026-11-17, read 2026-11-18. — FIRST EPSS

Related advisories

Sources

  1. NVD
  2. Bluetooth SIG statement on BLUFFS
  3. Microsoft Security Update Guide: CVE-2023-24023
  4. Espressif AR2023-010: Security Advisory Concerning the Bluetooth BLUFFS Vulnerability
  5. u-blox Security Advisory for Bluetooth BLUFFS Vulnerability (CVE-2023-24023)
  6. Debian security tracker: CVE-2023-24023
  7. CISA KEV
  8. FIRST EPSS

Frequently asked questions

Does BLUFFS affect Bluetooth LE devices?

No. BLUFFS targets BR/EDR (Classic) session setup. u-blox states its LE-only products are not affected, and Espressif says only its ESP32 series, which has Bluetooth Classic, is affected (per the Bluetooth SIG, u-blox and Espressif).

Is my ESP32 product protected against CVE-2023-24023?

Espressif says the attack works regardless of ESP-IDF release, but its KNOB fix (minimum 7-octet key) is in maintained branches v4.3 to v5.2, and the BIAS fix is in v4.3.5, v4.4.4, v5.0.1 and v5.1. Build on a patched ESP-IDF version (per Espressif AR2023-010).

What is the main mitigation for CVE-2023-24023?

Enforce a minimum encryption key length of 7 octets (16 where Security Mode 4 Level 4 is possible), use Secure Connections Only mode, and terminate links that fall back from Secure Connections for a peer bonded with it (per the Bluetooth SIG).

Is CVE-2023-24023 exploited in the wild?

It is not in the CISA KEV catalog as of 2026-11-18 (catalog version 2026.11.17). FIRST EPSS gives it 0.0134, the 71.7th percentile, in the 2026-11-17 dataset (per CISA KEV and FIRST EPSS).