CVE-2021-0170
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 · uneditedExposure of Sensitive Information to an Unauthorized Actor in firmware for some Intel(R) PROSet/Wireless Wi-Fi in multiple operating systems and some Killer(TM) Wi-Fi in Windows 10 and 11 may allow an authenticated user to potentially enable information disclosure 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 · high confidenceInformation disclosure vulnerability in Intel PROSet/Wireless Wi-Fi and Killer Wi-Fi firmware allows an authenticated local user to potentially access sensitive information via local access to the affected system.
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< 11.8.90< 11.8.90< 12.0.85< 12.0.85< 12.0.85>= 14.0.0, < 14.1.60>= 15.0.0, < 15.0.35>= 14.0.0, < 14.1.60>= 15.0.0, < 15.0.35< 15.0.35< 22.60CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Wi-Fi adapter modelOpen Device Manager, expand Network adapters, and look for Intel PROSet/Wireless or Killer Wi-Fi adapter (e.g., Intel Wi-Fi 6 AX200, Intel AC 8260, etc.)Affected if The adapter model matches one of the affected products: AC 8260, AC 8265, AC 9260, AC 9560, Wi-Fi 6 AX200, Wi-Fi 6 AX201, Wi-Fi 6 AX210, or Proset AC 3165
-
Retrieve the current firmware versionUse Intel PROSet Wireless diagnostic tool, or run 'netsh wlan show drivers' in Command Prompt, or check firmware version via Device Manager under the adapter properties Details tab looking for 'Firmware Version'Affected if The displayed firmware version is readable and can be compared against the affected ranges
-
Compare firmware version for AC 8260/8265If adapter is AC 8260 or AC 8265, check if firmware version is less than 11.8.90Affected if Firmware version < 11.8.90 for AC 8260 or AC 8265
-
Compare firmware version for AC 9260/9560If adapter is AC 9260 or AC 9560, check if firmware version is less than 12.0.85Affected if Firmware version < 12.0.85 for AC 9260 or AC 9560
-
Compare firmware version for Wi-Fi 6 AX200/AX201/AX210If adapter is AX200, AX201, or AX210: check if version < 12.0.85 OR between 14.0.0 and 14.1.60 (exclusive) OR between 15.0.0 and 15.0.35 (exclusive)Affected if Firmware version falls into any of the vulnerable ranges: < 12.0.85, >= 14.0.0 and < 14.1.60, or >= 15.0.0 and < 15.0.35 for AX200/AX201/AX210
-
Compare firmware version for AC 3165If adapter is Proset AC 3165, check if firmware version is less than 22.60Affected if Firmware version < 22.60 for AC 3165
The system is affected if an Intel Wi-Fi adapter from the list is installed with a firmware version matching any of the vulnerable version ranges provided.
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.
dbcve · scoped11.8.9012.0.8514.1.60
Apply vendor-supplied firmware updates for affected Intel PROSet/Wireless and Killer Wi-Fi adapters; verify patch deployment across all affected endpoints.
Upgrade to firmware version 11.8.90 or later (for 8260/8265), 12.0.85 or later (for 9260/9560 and early AX200/AX201/AX210), 14.1.60 or later, 15.0.35 or later (for AX200/AX201/AX210), or 22.60 or later (for 3165) depending on the specific adapter model
- Identify the exact wireless adapter model by checking Device Manager or system documentation
- Determine the current firmware version installed on the wireless adapter
- Based on the adapter model, upgrade to the minimum fixed version: For Intel Wi-Fi 6 AX200/AX201/AX210: upgrade to 12.0.85, 14.1.60, or 15.0.35 or later | For Intel AC 8260/8265: upgrade to 11.8.90 or later | For Intel AC 9260/9560: upgrade to 12.0.85 or later | For Intel PROSet Wireless 3165: upgrade to 22.60 or later
- Download the appropriate firmware update from the Intel Support website (downloadcenter.intel.com) or use the Intel PROSet/Wireless Software update utility
- Apply the firmware update following Intel's standard update procedure, which typically requires administrator privileges and may involve a system restart
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2021-0170 — 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-2021-0170 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