dbcve.org
Amt Ac 8260 FirmwareOperating system · Intel

CVE-2021-0177

MEDIUM · 6.5 CVSS v3.1 Published 2022-02-09
Fix available
A fix is available. Upgrade to 11.8.90 / 12.0.85 or later.
See remediation →
70/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
Improper 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 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 confidence

This vulnerability involves improper validation of consistency within input data in Intel PROSet/Wireless Wi-Fi and Killer Wi-Fi drivers for Windows 10 and 11, which could allow an unauthenticated attacker within Wi-Fi range to cause a denial of service via adjacent network access.

MitigationApply vendor-supplied firmware/driver updates from Intel or the hardware OEM as soon as available; in the interim, disable Wi-Fi when not in use and employ network segmentation to limit exposure to adjacent attackers.

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
Amt Ac 8260 FirmwareOperating system
Affected:< 11.8.90
Amt Ac 8265 FirmwareOperating system
Affected:< 11.8.90
Amt Ac 9260 FirmwareOperating system
Affected:< 12.0.85
Amt Ac 9560 FirmwareOperating system
Affected:< 12.0.85
Amt Wi Fi 6 Ax200 FirmwareOperating system
Affected:< 12.0.85>= 14.0.0, < 14.1.60>= 15.0.0, < 15.0.35
Amt Wi Fi 6 Ax201 FirmwareOperating system
Affected:>= 14.0.0, < 14.1.60>= 15.0.0, < 15.0.35
Amt Wi Fi 6 Ax210 FirmwareOperating system
Affected:< 15.0.35
Proset Ac 3165 FirmwareOperating system
Affected:< 22.60

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Wi-Fi adapter model
    Open Device Manager, expand Network adapters, and note the Intel wireless adapter name (e.g., Intel Wi-Fi 6 AX200, Intel AC 8265, etc.)
    Affected if The adapter is one 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
  2. Locate firmware version in Intel PROSet
    Open Intel PROSet Wireless (or Killer Control Center for Killer adapters), navigate to the adapter properties or advanced settings, and record the firmware version number shown
    Affected if Firmware version cannot be retrieved via this method
  3. Retrieve firmware version via Device Manager
    In Device Manager, right-click the wireless adapter, select Properties, go to the Details tab, choose 'Firmware version' from the Property dropdown, and record the version shown
    Affected if Firmware version displays as unknown or cannot be read
  4. Compare AC 8260/8265 version against threshold
    If using Intel AC 8260 or AC 8265, compare the firmware version to 11.8.90 - any version below 11.8.90 is affected
    Affected if Firmware version < 11.8.90 for AC 8260 or AC 8265
  5. Compare AC 9260/9560 version against threshold
    If using Intel AC 9260 or AC 9560, compare the firmware version to 12.0.85 - any version below 12.0.85 is affected
    Affected if Firmware version < 12.0.85 for AC 9260 or AC 9560
  6. Compare AX200/AX201/AX210 version against thresholds
    For AX200/AX201: check if version < 14.1.60 OR between 14.x.x and 15.0.34 (i.e., >= 14.0.0 and < 14.1.60, or >= 15.0.0 and < 15.0.35). For AX210: check if version < 15.0.35
    Affected if AX200/AX201 meets: version < 14.1.60, OR (version >= 14.0.0 and < 14.1.60), OR (version >= 15.0.0 and < 15.0.35); AX210: version < 15.0.35

Your environment is affected if the Wi-Fi adapter matches one of the affected models AND the installed firmware version falls within the specific version ranges listed for that adapter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 11.8.90 / 12.0.85 / 14.1.60 or later
Fixed in 11.8.9012.0.8514.1.60
Interim mitigation

Apply vendor-supplied firmware/driver updates from Intel or the hardware OEM as soon as available; in the interim, disable Wi-Fi when not in use and employ network segmentation to limit exposure to adjacent attackers.

Recommended fix High confidence

Firmware >= 11.8.90 (8260/8265), >= 12.0.85 (9260/9560/AX200 older), >= 14.1.60 (AX200 14.x), >= 15.0.35 (AX200 15.x/AX201/AX210), >= 22.60 (3165)

  1. 1. Identify the exact Intel Wi-Fi adapter model in the affected system (e.g., AX200, AX201, AX210, etc.)
  2. 2. Download the latest Intel Wi-Fi firmware update from the official Intel support website or through the Intel Driver & Support Assistant
  3. 3. Install the appropriate firmware version for your adapter: For AC 8260/8265, upgrade to firmware >= 11.8.90; For AC 9260/9560 or AX200 (older branch), upgrade to firmware >= 12.0.85; For AX200 (14.x branch), upgrade to firmware >= 14.1.60; For AX200 (15.x branch), AX201, or AX210, upgrade to firmware >= 15.0.35; For Proset AC 3165, upgrade to firmware >= 22.60
  4. 4. Reboot the system after applying the firmware update
  5. 5. Verify the installed firmware version matches the fixed release using device manager or Intel PROSet utility
Caveat Firmware updates may temporarily disconnect network during installation; ensure stable power and backup connectivity options

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Amt Ac 8260 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-0177 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-0177 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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