CVE-2021-0178
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 · uneditedImproper input validation in software for Intel(R) PROSet/Wireless Wi-Fi and Killer(TM) Wi-Fi in Windows 10 and 11 may allow an unauthenticated user to potentially enable denial of service via adjacent 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 confidenceImproper input validation in Intel(R) PROSet/Wireless Wi-Fi and Killer(TM) Wi-Fi drivers for Windows 10 and 11 allows an unauthenticated attacker within adjacent network range to potentially cause denial of service via specially crafted input.
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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the wireless adapter modelOpen Device Manager, expand Network adapters, and look for Intel or Killer Wi-Fi adapters (e.g., Intel Wi-Fi 6 AX200, AX201, AX210, AC8265, AC9260, etc.)Affected if The system uses one of the affected adapter models listed in the CVE (8260, 8265, 9260, 9560, AX200, AX201, AX210, or 3165)
-
Check the firmware/driver versionIn Device Manager, right-click the wireless adapter, select Properties, go to the Driver tab, and note the Driver Version. For firmware version specifically, you can also use the Intel PROSet Wireless software utility or run 'netsh wlan show drivers' in Command PromptAffected if The displayed version number is lower than the fixed versions (11.8.90 for 8260/8265, 12.0.85 for 9260/9560, 14.1.60/15.0.35 for AX200/AX201/AX210, or 22.60 for 3165)
-
Confirm the adapter is actively usedVerify the wireless adapter is enabled and connected or has capacity to connect, by checking Device Manager status or running 'netsh wlan show interfaces'Affected if The adapter shows as enabled and capable of wireless communication (the vulnerability is exploitable via adjacent network range)
A user is affected if they have one of the listed Intel or Killer wireless adapters with a firmware version that falls below the fixed version numbers for their specific model.
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 the Intel or Killer vendor-provided driver/software updates that address the input validation vulnerability.
Firmware version 11.8.90 or later for 8260/8265; 12.0.85 or later for 9260/9560/AX200; 14.1.60 or later for AX201/AX200 (14.x branch); 15.0.35 or later for AX201/AX200/AX210 (15.x branch); 22.60 or later for 3165
- Identify the exact Intel Wi-Fi adapter model (e.g., AX200, AX201, AX210, 8260, 8265, 9260, 9560, 3165) in the system using Device Manager or Intel PROSet/Wireless tools
- Navigate to the Intel download center or support page for wireless adapters
- Search for the specific adapter model and download the latest firmware version matching or exceeding: 11.8.90 for 8260/8265, 12.0.85 for 9260/9560/AX200, 14.1.60 for AX201/AX200 (14.x branch), 15.0.35 for AX201/AX200/AX210 (15.x branch), or 22.60 for 3165
- Update the wireless adapter firmware using Intel PROSet/Wireless Wi-Fi driver software, or follow Intel's firmware update utility instructions
- After update, verify the firmware version in Device Manager to confirm the installed version is at or above the fixed version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-0178 — 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-0178 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