Adjacent information disclosure via driver type confusion
Published May 9, 2023 · Updated Jul 10, 2025
Type confusion in the Windows Bluetooth driver in affected Windows builds allows physically proximate attackers to read sensitive memory. Microsoft has not published which driver routine accesses a resource using an incompatible type or how crafted Bluetooth traffic reaches it. The attacker must be within Bluetooth range; authentication and user interaction are not required, and the documented impact is memory disclosure only.
Summary
What happened
Type confusion in the Windows Bluetooth driver in affected Windows builds allows physically proximate attackers to read sensitive memory. Microsoft has not published which driver routine accesses a resource using an incompatible type or how crafted Bluetooth traffic reaches it. The attacker must be within Bluetooth range; authentication and user interaction are not required, and the documented impact is memory disclosure only.
The record
- CVE
- CVE-2023-24944
- Published
- May 9, 2023
- Updated
- Jul 10, 2025
- Vendor
- Microsoft
- Product
- Windows Server 2019
- Classifications
- CWE-843, T1210
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 9, 2023CVE publishedPublication date reported by the CVE source.
- Jul 10, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=10.0.17763.0 <10.0.17763.4377
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo