CVE-2021-0162
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 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 confidenceImproper input validation in Intel PROSet/Wireless Wi-Fi and Killer Wi-Fi drivers for Windows 10 and 11 allows an unauthenticated attacker with adjacent network access to potentially escalate privileges. The vulnerability stems from insufficient validation of input data in the Wi-Fi software stack, likely during driver communication or firmware interaction.
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 Wi-Fi adapter modelOpen Device Manager, expand Network adapters, look for Intel wireless adapters (e.g., Intel Wi-Fi 6 AX200, Intel Dual Band Wireless-AC 8260, etc.) and note the exact model nameAffected if The adapter model matches any of: 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 Intel wireless firmware versionIn Device Manager, right-click the Intel wireless adapter, select Properties, go to the Details tab, and select Firmware version from the Property dropdown. Alternatively, open Intel PROSet/Wireless software and check the adapter firmware version in the adapter settings or diagnosticsAffected if The displayed firmware version is lower than the fixed versions for your specific adapter model (11.8.90 for 8260/8265, 12.0.85 for 9260/9560/AX200, 14.1.60 for AX200/AX201 if between 14.0.0-14.x, 15.0.35 for AX200/AX201/AX210 if 15.x, or 22.60 for AC 3165)
-
Verify Intel PROSet/Wireless driver versionOpen Programs and Features (appwiz.cpl) and look for Intel PROSet/Wireless software, or right-click the wireless adapter in Device Manager, select Properties, and check the Driver tab for the driver versionAffected if The driver version is older than the patched release, as the vulnerability exists in the driver software stack
-
Confirm adjacent network exposureReview system configuration to determine if Wi-Fi is enabled and the system connects to networks where untrusted adjacent attackers could be present (e.g., public Wi-Fi, corporate networks with guest access)Affected if Wi-Fi is active and the system operates in an environment where unauthenticated adjacent network attackers could reach the wireless interface
The system is affected if it has any of the listed Intel wireless adapters (8260, 8265, 9260, 9560, AX200, AX201, AX210, AC 3165) with firmware versions below the fixed releases AND Wi-Fi is enabled and accessible to adjacent attackers.
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 patches for Intel PROSet/Wireless Wi-Fi or Killer Wi-Fi drivers. Prioritize systems with elevated privileges or network exposure. Verify the installed Wi-Fi driver version matches the patched release.
Intel PROSet/Wireless Wi-Fi driver/firmware version meeting or exceeding: 11.8.90 (AC 8260/8265), 12.0.85 (AC 9260/9560, AX200 pre-14.x), 14.1.60 (AX200/AX201 14.x series), 15.0.35 (AX200/AX201 15.x series, AX210), or 22.60 (Proset AC 3165)
- 1. Identify the exact wireless adapter model in the system (e.g., AX200, AX201, AX210, etc.) using Device Manager or Intel Driver & Support Assistant.
- 2. Visit the Intel Support website and locate the driver/firmware download page for the specific adapter model.
- 3. Download and install the latest Intel PROSet/Wireless Wi-Fi driver and firmware package that meets or exceeds the fixed version for your adapter: For AC 8260/8265: 11.8.90 or later; For AC 9260/9560: 12.0.85 or later; For Wi-Fi 6 AX200 (pre-14.x): 12.0.85 or later; For Wi-Fi 6 AX200 (14.x series): 14.1.60 or later; For Wi-Fi 6 AX200 (15.x series): 15.0.35 or later; For Wi-Fi 6 AX201 (14.x or 15
- 4. Restart the system after driver/firmware installation to ensure the new firmware is properly loaded.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-0162 — 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-0162 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