dbcve.org
Windows 10 21h2Operating system · Microsoft

CVE-2024-21306

MEDIUM · 5.7 CVSS v3.1 Published 2024-01-09
Fix available
A fix is available. Upgrade to 10.0.19044.3930 / 10.0.19045.3930 or later.
See remediation →
60/100
Remediation priority · Elevated
No privileges Patch available

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
Microsoft Bluetooth Driver Spoofing Vulnerability

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
How this class of weakness works · CWE-306

A sensitive function is reachable with no authentication at all, so anyone who finds the endpoint can use it. These are routinely discovered by automated scanning. The fix is to require and enforce authentication on every privileged path, with no exceptions left open.

General guidance for the missing authentication class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
Windows 10 21h2Operating system
Affected:< 10.0.19044.3930
Windows 10 22h2Operating system
Affected:< 10.0.19045.3930
Windows 11 21h2Operating system
Affected:< 10.0.22000.2713
Windows 11 22h2Operating system
Affected:< 10.0.22621.3007
Windows 11 23h2Operating system
Affected:< 10.0.22631.3007
Windows Server 2022Operating system
Affected:< 10.0.20348.2227
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.643

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
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

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.19044.3930 / 10.0.19045.3930 / 10.0.20348.2227 or later
Fixed in 10.0.19044.393010.0.19045.393010.0.20348.2227
Vendor patch msrc.microsoft.com →
Recommended fix High confidence

Upgrade to the respective build: Windows 10 21h2 to 10.0.19044.3930, Windows 10 22h2 to 10.0.19045.3930, Windows 11 21h2 to 10.0.22000.2713, Windows 11 22h2 to 10.0.22621.3007, Windows 11 23h2 to 10.0.22631.3007, Windows Server 2022 to 10.0.20348.2227, or Windows Server 2022 23h2 to 10.0.25398.643

  1. Identify the exact Windows version and build by running 'winver' or 'systeminfo' in Command Prompt
  2. Open Windows Update: Settings > Update & Security > Windows Update
  3. Click 'Check for updates' to download and install the cumulative security update containing the fix
  4. Alternatively, download the specific security update from Microsoft Update Catalog: https://catalog.update.microsoft.com/
  5. For the fixed builds, ensure installation of: Windows 10 21h2 KB5034123 (build 10.0.19044.3930), Windows 10 22h2 KB5034123 (build 10.0.19045.3930), Windows 11 21h2 KB5034122 (build 10.0.22000.2713), Windows 11 22h2 KB5034122 (build 10.0.22621.3007), Windows 11 23h2 KB5034122 (build 10.0.22631.3007), Windows Server 2022 KB5034124 (build 10.0.20348.2227), or Windows Server 2022 23h2 KB5034124 (build
  6. Restart the system after installation
  7. Verify the installed build matches the fixed version using 'winver'
Caveat Standard Windows cumulative update—may require restart; no major functionality changes expected for this security-only update

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-21306 — 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-2024-21306 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