# CVE-2024-21306: Microsoft Bluetooth Driver Spoofing Vulnerability

> Attackers can spoof Bluetooth devices due to missing authentication in the Microsoft Bluetooth Driver, bypassing security controls.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Jan 2024
- **Updated:** 3 May 2025
- **Also known as:** GHSA-6fjx-3c25-3qrc

## What is CVE-2024-21306?

CVE-2024-21306 is a medium-severity authentication bypass vulnerability in Microsoft Windows 10 21h2, published on 9 Jan 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Microsoft Bluetooth Driver Spoofing Vulnerability

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2024-21306?

It affects 7 products.


Products: Microsoft Windows 10 21h2, Microsoft Windows 10 22h2, Microsoft Windows 11 21h2, Microsoft Windows 11 22h2, Microsoft Windows 11 23h2, Microsoft Windows Server 2022, Microsoft Windows Server 2022 23h2.

## How do I fix CVE-2024-21306?

No fix has been published for CVE-2024-21306 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-21306 being exploited?

There is no known exploitation of CVE-2024-21306 in the wild and no public exploit code.

Public exploit code:

- Exploit basado en vulnerabilidades criticas Bluetooth (CVE-2023-45866, CVE-2024-21306) (github_poc): https://github.com/Danyw24/blueXploit
- CVE-2024-21306 BadBlue implementation (Using DuckyScript) (github_poc): https://github.com/PhucHauDeveloper/BadBlue
- https://github.com/d4rks1d33/C-PoC-for-CVE-2024-21306 (github_poc): https://github.com/d4rks1d33/C-PoC-for-CVE-2024-21306

## Other vulnerabilities in Microsoft Windows 10 21h2

- [CVE-2025-21333](https://insights.sbomify.com/CVE-2025-21333/): Microsoft Windows Hyper-V NT Kernel Integration VSP Heap-based Buffer Overflow (high 7.8, exploited in the wild)
- [CVE-2025-21334](https://insights.sbomify.com/CVE-2025-21334/): Microsoft Windows Hyper-V NT Kernel Integration VSP Use-After-Free (high 7.8, exploited in the wild)
- [CVE-2025-21335](https://insights.sbomify.com/CVE-2025-21335/): Microsoft Windows Hyper-V NT Kernel Integration VSP Use-After-Free (high 7.8, exploited in the wild)
- [CVE-2026-42904](https://insights.sbomify.com/CVE-2026-42904/): Windows TCP/IP Elevation of Privilege Vulnerability (critical 9.6)
- [CVE-2026-105733](https://insights.sbomify.com/CVE-2026-105733/): Windows Hyper-V Remote Code Execution Vulnerability (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-21306 and fix it if it is affected.

What it is: CVE-2024-21306 is a medium-severity authentication bypass vulnerability in Microsoft Windows 10 21h2, published on 9 Jan 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-21306 in the wild and no public exploit code.

Affected product: Microsoft Windows 10 21h2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-21306/ (Markdown: https://insights.sbomify.com/CVE-2024-21306/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-21306
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-21306
- OSV: https://osv.dev/vulnerability/CVE-2024-21306

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-21306/
Summaries are generated and may contain mistakes; the official description above is the record.