CVE-2022-30144
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 · uneditedWindows Bluetooth Service Remote Code Execution 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 confidenceA vulnerability in the Windows Bluetooth Service allows remote attackers to execute arbitrary code by sending specially crafted Bluetooth communications to a targeted Windows system. The flaw exists in how the Bluetooth service handles certain malformed requests, leading to memory corruption that can be leveraged for code execution.
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 dataall versions= 20h2= 21h1= 1607= 1809all versionsall versionsall versionsCVSS 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
- High
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Determine if the system has Bluetooth hardwareOpen Device Manager and expand 'Bluetooth' to see if any Bluetooth adapters are listed, or run 'Get-PnpDevice -Class Bluetooth' in PowerShellAffected if Bluetooth adapters are present in Device Manager or listed by the PowerShell cmdlet
-
Check if the Bluetooth service is runningOpen Services (services.msc) and locate the 'Bluetooth Support Service' (bthserv), or run 'sc query bthserv' in Command PromptAffected if The Bluetooth service state shows as RUNNING
-
Verify the Windows version is affectedRun 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify the Windows versionAffected if The system runs Windows 10 (any version including 20h2, 21h1, 1607, 1809), Windows 11, Windows 8.1, or Windows Rt 8.1
-
Confirm the Bluetooth service is enabled for remote connectionsCheck Bluetooth settings in Settings > Devices > Bluetooth & other devices to ensure Bluetooth is turned on and the system is discoverableAffected if Bluetooth is enabled and the system accepts Bluetooth connections
The system is likely affected if it runs an affected Windows version, has Bluetooth hardware, and has the Bluetooth service enabled and running.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply the Microsoft security update for CVE-2022-30144 to all affected Windows systems. If immediate patching is not possible, consider disabling the Bluetooth service or blocking Bluetooth-related network traffic as a compensating control.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30144 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-30144 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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