dbcve.org
Bluetooth Core SpecificationApplication · Bluetooth

CVE-2023-24023

MEDIUM · 6.8 CVSS v3.1 Published 2023-11-28
Fix available
A fix is available. Upgrade to 10.0.17763.5122 / 10.0.19043.3693 or later.
See remediation →
73/100
Remediation priority · Elevated
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This vulnerability in Bluetooth BR/EDR (Classic Bluetooth) allows man-in-the-middle attackers to force the use of a short encryption key during the Secure Simple Pairing or Secure Connections pairing process defined in Bluetooth Core Specification 4.2 through 5.4. Attackers can exploit this to discover the encryption key and perform live injection attacks.

MitigationOrganizations should inventory Bluetooth-enabled devices, apply vendor firmware updates as they become available, and consider using higher-assurance pairing methods or avoiding Bluetooth in untrusted environments until patches are deployed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Bluetooth Core SpecificationApplication
Affected:>= 4.2, <= 5.4
Windows 10 1809Operating system
Affected:< 10.0.17763.5122
Windows 10 21h2Operating system
Affected:< 10.0.19043.3693
Windows 10 22h2Operating system
Affected:< 10.0.19045.3693
Windows 11 21h2Operating system
Affected:< 10.0.22000.2600
Windows 11 22h2Operating system
Affected:< 10.0.22621.2715
Windows 11 23h2Operating system
Affected:< 10.0.22631.2715
Windows Server 2019Operating system
Affected:< 10.0.17763.5122

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Windows build version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to obtain the exact build number
    Affected if Build number is below 17763.5122 for Windows 10 1809/Server 2019, below 19043.3693 for Windows 10 21h2, below 19045.3693 for Windows 10 22h2, below 22000.2600 for Windows 11 21h2, below 22621.2715 for Windows 11 22h2, or below 22631.2715 for Windows 11 23h2
  2. Verify Bluetooth is enabled
    Check Device Manager for Bluetooth radio or run 'Get-PnpDevice -Class Bluetooth' in PowerShell
    Affected if Bluetooth adapter is present and enabled on a vulnerable Windows build
  3. Confirm Secure Simple Pairing or Secure Connections is in use
    Inspect pairing method during Bluetooth device connection by monitoring Bluetooth traffic or checking adapter properties in Settings > Bluetooth & devices
    Affected if Pairing occurs using Secure Simple Pairing or Secure Connections protocols on a vulnerable implementation

A user is affected if they are running a Windows version with a build number below the specified thresholds AND have Bluetooth enabled and actively pairing devices using Secure Simple Pairing or Secure Connections.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.17763.5122 / 10.0.19043.3693 / 10.0.19045.3693 or later
Fixed in 10.0.17763.512210.0.19043.369310.0.19045.3693
Interim mitigation

Organizations should inventory Bluetooth-enabled devices, apply vendor firmware updates as they become available, and consider using higher-assurance pairing methods or avoiding Bluetooth in untrusted environments until patches are deployed.

Recommended fix High confidence

Windows: Install KB5023773 or subsequent security updates for the respective Windows version (exact KB varies by Windows edition and version)

  1. Check current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Identify the specific Windows edition and build number from the output
  3. Navigate to Windows Update via Settings > Update & Security > Windows Update
  4. Check for available updates and install all pending security updates
  5. Verify the update installed successfully by checking the Windows version matches or exceeds: Windows 10 1809: 10.0.17763.5122, Windows 10 21h2: 10.0.19043.3693, Windows 10 22h2: 10.0.19045.3693, Windows 11 21h2: 10.0.22000.2600, Windows 11 22h2: 10.0.22621.2715, Windows 11 23h2: 10.0.22631.2715, Windows Server 2019: 10.0.17763.5122
  6. For non-Windows devices, contact the device manufacturer for Bluetooth firmware updates implementing the BLUFFS fix
Caveat Security update only; no functional changes expected. Ensure Bluetooth devices remain compatible after update.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Bluetooth Core Specification Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,320.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-24023 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-24023 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data