dbcve.org
Windows 10Operating system · Microsoft

CVE-2022-44674

MEDIUM · 5.5 CVSS v3.1 Published 2022-12-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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
Windows Bluetooth Driver Information Disclosure 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 · moderate confidence

This is an information disclosure vulnerability in the Windows Bluetooth driver. The vulnerability allows a local attacker to potentially access sensitive information through the Bluetooth driver component. CVSS 5.5 indicates medium severity with local attack vector and low complexity.

MitigationApply the Microsoft security update for CVE-2022-44674 to affected Windows systems. Verify Bluetooth driver version after patching.

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
Windows 10Operating system
Affected:all versions= 20h2= 21h1= 21h2= 22h2= 1607= 1809
Windows 11Operating system
Affected:all versions= 22h2
Windows Server 2016Operating system
Affected:all versions
Windows Server 2019Operating system
Affected:all versions
Windows Server 2022Operating system
Affected:all versions

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 if Windows version is in affected list
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify your Windows version. Affected versions include Windows 10 (20h2, 21h1, 21h2, 22h2, 1607, 1809), Windows 11 (22h2), and Windows Server 2016, 2019, 2022.
    Affected if Your Windows version matches one of the listed affected versions (any version of 10, 11 22h2, or Server 2016/2019/2022)
  2. Verify Bluetooth hardware is present
    Open Device Manager, expand 'Bluetooth', or run 'Get-PnpDevice -Class Bluetooth' in PowerShell to list Bluetooth devices.
    Affected if Bluetooth hardware is listed as present and enabled on the system
  3. Check Bluetooth driver version
    In Device Manager, right-click each Bluetooth device, select Properties, go to Driver tab, and note the Driver Version. Alternatively, run 'Get-WmiObject Win32_PnPSignedDriver | Where-Object {$_.DeviceName -like "*Bluetooth*"} | Select-Object DeviceName, DriverVersion, DriverDate' in PowerShell.
    Affected if The Bluetooth driver version is present and matches a version released before Microsoft's security patch for this CVE
  4. Inspect Bluetooth driver file version
    Navigate to C:\Windows\System32\drivers\ and locate bth.sys or bthport.sys. Right-click the file, select Properties, and check the File Version on the Details tab.
    Affected if The driver file version is earlier than the patched version released by Microsoft in December 2022 or January 2023 security updates
  5. Check for recent security updates
    Run 'wmic qfe list' or open Settings > Windows Update > Update history to see installed security updates. Look for updates from December 2022 or January 2023 that include CVE-2022-44674 in the description.
    Affected if No security update addressing CVE-2022-44674 has been installed on the system

You are affected if your system runs a vulnerable Windows version with Bluetooth enabled and the Bluetooth driver has not been updated via the December 2022 or January 2023 Microsoft security patches.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Microsoft security update for CVE-2022-44674 to affected Windows systems. Verify Bluetooth driver version after patching.

Recommended fix Moderate confidence

December 2022 Windows Security Update (or later) for your specific Windows version

  1. Apply the December 2022 Windows Security Update (or subsequent updates) which addresses the Windows Bluetooth Driver Information Disclosure vulnerability (CVE-2022-44674)
  2. Open Windows Update and check for updates, or deploy the update via your organization's patch management system
  3. Verify the update installed successfully by checking Windows Update history for the December 2022 security patches

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

Fix this in Windows 10 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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