dbcve.org
Ax210 FirmwareOperating system · Intel

CVE-2021-0152

MEDIUM · 5.5 CVSS v3.1 Published 2021-11-17
Fix available
A fix is available. Upgrade to 22.60 or later.
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
Improper verification of cryptographic signature in the installer for some Intel(R) Wireless Bluetooth(R) and Killer(TM) Bluetooth(R) products in Windows 10 may allow an authenticated user to potentially enable denial of service via local access.

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

Improper cryptographic signature verification in the Windows 10 installer for Intel Wireless Bluetooth and Killer Bluetooth products allows an authenticated local user to potentially cause denial of service. The vulnerability exists in the installer's failure to properly validate digital signatures before execution.

MitigationApply vendor-supplied updates from Intel or Killer for the affected Bluetooth installer packages. Since this is a vendor installer vulnerability, organizations should obtain patched installers from the vendor and redeploy to affected systems.

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
Ax210 FirmwareOperating system
Affected:< 22.60
Ax201 FirmwareOperating system
Affected:< 22.60
Ax200 FirmwareOperating system
Affected:< 22.60
Ac 9560 FirmwareOperating system
Affected:< 22.60
Ac 9462 FirmwareOperating system
Affected:< 22.60
Ac 9461 FirmwareOperating system
Affected:< 22.60
Ac 9260 FirmwareOperating system
Affected:< 22.60
Ac 8265 FirmwareOperating system
Affected:< 22.60

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Intel Wi-Fi/Bluetooth adapter model
    Open Device Manager, expand 'Network adapters' and 'Bluetooth', look for Intel wireless adapters (Ax200, Ax201, Ax210, Ac9560, Ac9462, Ac9461, Ac9260, Ac8265)
    Affected if An affected Intel Wi-Fi/Bluetooth adapter model is present in the system
  2. Check Intel Bluetooth driver version
    In Device Manager, right-click the Intel Bluetooth device, select Properties, go to the Driver tab, note the Driver Version
    Affected if The driver version is below 22.60 (the vulnerable installer version range)
  3. Verify Intel Wireless driver package version
    Open Programs and Features (appwiz.cpl), look for 'Intel(R) Wi-Fi' or 'Intel(R) Wireless Bluetooth' driver package, check the version column
    Affected if The installed Intel wireless/Bluetooth driver package version is below 22.60
  4. Inspect Intel driver installation date and source
    In Device Manager, check driver details for the Bluetooth device, note the Driver Date and Driver Version, compare to Intel's 22.60 release timeline
    Affected if Driver version indicates installation from a package predating the 22.60 patch

A system is affected if it contains any of the listed Intel Wi-Fi/Bluetooth adapters and has an installed driver/installer version below 22.60, since the vulnerability resides in the Windows installer package's signature verification failure.

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
Upgrade available Upgrade to 22.60 or later
Fixed in 22.60
Interim mitigation

Apply vendor-supplied updates from Intel or Killer for the affected Bluetooth installer packages. Since this is a vendor installer vulnerability, organizations should obtain patched installers from the vendor and redeploy to affected systems.

Recommended fix High confidence

Firmware version 22.60 or later for the respective adapter (Ax210, Ax201, Ax200, Ac9560, Ac9462, Ac9461, Ac9260, Ac8265)

  1. Identify the specific Intel or Killer wireless adapter model in the system (e.g., AX210, AX201, AX200, AC9560, etc.)
  2. Download the latest Intel Wireless Bluetooth driver package for Windows 10 from the official Intel support website
  3. Run the installer and follow the on-screen prompts to update the Bluetooth firmware and driver
  4. Verify the installed version matches 22.60 or later via Windows Device Manager under Bluetooth adapters

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

Fix this in Ax210 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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