CVE-2021-0163
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 Validation of Consistency within input 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 escalation of privilege 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 confidenceA vulnerability in Intel PROSet/Wireless and Killer WiFi drivers for Windows 10/11 allows improper validation of input data consistency. An unauthenticated attacker within WiFi range can exploit this to escalate privileges on the target 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/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.
-
Identify installed Intel WiFi adapterOpen Device Manager, expand Network adapters, and look for Intel wireless adapters (e.g., Intel Wi-Fi 6 AX200, Intel(R) Wireless-AC 9560, etc.) or run `Get-NetAdapter | Where-Object {$_.Name -like '*Intel*' -or $_.Name -like '*Wi-Fi*'}`Affected if The system has an Intel WiFi adapter matching the affected model names (8260, 8265, 9260, 9560, AX200, AX201, AX210, 3165)
-
Retrieve WiFi firmware versionIn Device Manager, right-click the Intel WiFi adapter, select Properties, go to the Driver tab, and check the Firmware Version field. Alternatively, open Intel PROSet/Wireless software and navigate to the firmware version display, or use `netsh wlan show drivers` and check driver detailsAffected if A firmware version is displayed for an affected Intel WiFi adapter
-
Check firmware version for Intel AC 8260/8265Compare your installed firmware version against the affected range: versions below 11.8.90 are vulnerableAffected if Firmware version < 11.8.90 on Intel AC 8260 or 8265 adapters
-
Check firmware version for Intel AC 9260/9560Compare your installed firmware version against the affected range: versions below 12.0.85 are vulnerableAffected if Firmware version < 12.0.85 on Intel AC 9260 or 9560 adapters
-
Check firmware version for Intel WiFi 6 AX200/AX201/AX210Compare your installed version against three vulnerable ranges: < 12.0.85, OR >= 14.0.0 and < 14.1.60, OR >= 15.0.0 and < 15.0.35Affected if Firmware version falls into any of these ranges: < 12.0.85, >= 14.0.0 and < 14.1.60, or >= 15.0.0 and < 15.0.35 on AX200, AX201, or AX210 adapters
-
Check firmware version for Intel PROSet AC 3165Compare your installed firmware version against the affected range: versions below 22.60 are vulnerableAffected if Firmware version < 22.60 on Intel PROSet AC 3165 adapter
Your system is affected if it contains an Intel WiFi adapter from the affected product list AND the installed firmware version falls within any of the vulnerable version ranges specified for that adapter.
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 WiFi drivers to patched versions provided by Intel or Killer. Prioritize systems with wireless connectivity in high-security environments.
Firmware >= 11.8.90 (Amt Ac 8260/8265), >= 12.0.85 (Amt Ac 9260/9560, AX200), >= 14.1.60 or >= 15.0.35 (AX201), >= 15.0.35 (AX210), >= 22.60 (Proset 3165)
- 1. Identify the exact wireless adapter model in the system using Device Manager (look under Network adapters) or by running 'wmic nic get name,guid'
- 2. Note the current firmware version - this can typically be found in the driver properties in Device Manager or via Intel PROSet/Wireless or Killer Control Center software
- 3. Download the appropriate firmware/driver update from Intel's support site (www.intel.com) or through the Intel PROSet/Wireless software update feature
- 4. For the affected models: Amt Ac 8260/8265 upgrade to firmware >= 11.8.90; Amt Ac 9260/9560 upgrade to >= 12.0.85; Wi-Fi 6 AX200: upgrade to >= 12.0.85 OR >= 14.1.60 OR >= 15.0.35; Wi-Fi 6 AX201: upgrade to >= 14.1.60 OR >= 15.0.35; Wi-Fi 6 AX210: upgrade to >= 15.0.35; Proset Ac 3165: upgrade to >= 22.60
- 5. Apply the firmware update following Intel's provided instructions - this typically requires administrator privileges and may require a system reboot
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-0163 — 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-0163 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