CVE-2021-0174
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 Use of Validation Framework 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 a 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 validation framework usage in Intel PROSet/Wireless and Killer Wi-Fi firmware allows an adjacent, unauthenticated attacker to potentially cause denial of service. The vulnerability exists in the firmware validation logic for Wi-Fi components, enabling a malformed input via adjacent network access to trigger a DoS condition.
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 Wi-Fi adapter modelOpen Device Manager, expand Network adapters, look for Intel or Killer wireless adapter (e.g., Intel Wi-Fi 6 AX200, Intel AC 8265, etc.)Affected if The adapter is any of: Intel AC 8260, AC 8265, AC 9260, AC 9560, Wi-Fi 6 AX200, Wi-Fi 6 AX201, Wi-Fi 6 AX210, or PROSet AC 3165
-
Check current firmware version via Intel PROSet/WirelessOpen Intel PROSet/Wireless software, go to Wireless Settings or Driver/Firmware version information. Alternatively, use command: netsh wlan show drivers and check firmware version field, or use Intel Driver & Support AssistantAffected if Firmware version cannot be determined or shows as unknown (vulnerability may still apply)
-
Compare firmware version against affected rangesMatch your adapter model and firmware version to: AC 8260/8265 < 11.8.90; AC 9260/9560 < 12.0.85; AX200 < 12.0.85 OR >=14.0.0 and <14.1.60 OR >=15.0.0 and <15.0.35; AX201 >=14.0.0 and <14.1.60 OR >=15.0.0 and <15.0.35; AX210 < 15.0.35; AC 3165 < 22.60Affected if Your firmware version falls within ANY of the listed vulnerable version ranges for your specific adapter model
-
Verify wireless interface is enabledCheck that Wi-Fi is turned on and the adapter is active in Device Manager or network connectionsAffected if The adapter is present but disabled (vulnerability not reachable while disabled)
-
Confirm adjacent network exposureVerify the system can receive Wi-Fi probe requests or is connected to a network (the attack requires adjacent network access, not remote)Affected if System Wi-Fi is actively scanning or connected to any wireless network
You are affected if you have any of the listed Intel or Killer Wi-Fi adapters with a firmware version lower than the fixed version for your specific model, and your Wi-Fi interface is enabled and can receive adjacent network traffic.
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
Update Wi-Fi firmware/drivers to vendor-provided patches. For Intel PROSet/Wireless, apply the latest firmware version from Intel's support site. For Killer Wi-Fi adapters, update through the vendor's driver/firmware updates.
Upgrade to firmware version 11.8.90 or later for 8260/8265; 12.0.85 or later for 9260/9560 and Ax200 (initial fix); 14.1.60 or later for Ax200/Ax201; 15.0.35 or later for Ax200/Ax201/Ax210; 22.60 or later for Proset 3165
- 1. Identify the exact Intel(R) wireless adapter model in your system (e.g., AX200, AX201, AX210, etc.) via Device Manager or system information.
- 2. Determine the current firmware version of the wireless adapter: Open Device Manager > expand Network adapters > right-click the Intel Wi-Fi adapter > select Properties > go to the Driver tab > note the driver version (firmware version may be shown in the Driver version field or in Advanced settings).
- 3. Download the appropriate Intel Wireless Bluetooth and Wi-Fi driver package for your specific adapter from the official Intel download center (www.intel.com).
- 4. Run the installer as Administrator to update the wireless adapter firmware to the fixed version: for Ax200/Ax201 upgrade to 14.1.60 or later, or 15.0.35 or later; for Ax210 upgrade to 15.0.35 or later; for 8260/8265 upgrade to 11.8.90 or later; for 9260/9560 upgrade to 12.0.85 or later; for Proset 3165 upgrade to 22.60 or later.
- 5. Restart the system after the firmware update completes to ensure the new firmware is properly loaded.
- 6. Verify the firmware version has been updated by checking the adapter properties in Device Manager.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-0174 — 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-0174 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