# CVE-2021-0177: Denial of service in Intel(R) PROSet/Wireless Wi-Fi and Killer(TM) Wi-Fi in Windows 10 and 11

> An unauthenticated attacker can cause a denial of service in Intel and Killer Wi-Fi drivers via adjacent network access due to improper input validation.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Feb 2022
- **Updated:** 5 May 2025
- **Also known as:** GHSA-5xhx-vcx5-c6qf

## What is CVE-2021-0177?

CVE-2021-0177 is a medium-severity denial of service vulnerability in Intel(R) PROSet/Wireless Wi-Fi and Killer(TM) Wi-Fi in Windows 10 and 11, published on 9 Feb 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2021-0177?

It affects 22 products.


Products: Intel Amt Ac 8260 Firmware, Intel Amt Ac 8265 Firmware, Intel Amt Ac 9260 Firmware, Intel Amt Ac 9560 Firmware, Intel Amt Wi-Fi 6 Ax200 Firmware, Intel Amt Wi-Fi 6 Ax201 Firmware, Intel Amt Wi-Fi 6 Ax210 Firmware, Intel Killer Ac 1550 Firmware, Intel Killer Wi-Fi 6 Ax1650 Firmware, Intel Killer Wi-Fi 6e Ax1675 Firmware, Intel Proset Ac 3165 Firmware, Intel Proset Ac 3168 Firmware, Intel Proset Ac 8260 Firmware, Intel Proset Ac 8265 Firmware, Intel Proset Ac 9260 Firmware, Intel Proset Ac 9461 Firmware, Intel Proset Ac 9462 Firmware, Intel Proset Ac 9560 Firmware, Intel Proset Wi-Fi 6 Ax200 Firmware, Intel Proset Wi-Fi 6 Ax201 Firmware and 2 more.

## How do I fix CVE-2021-0177?

No fix has been published for CVE-2021-0177 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-0177 being exploited?

There is no known exploitation of CVE-2021-0177 in the wild and no public exploit code.

## Other vulnerabilities in Intel(R) PROSet/Wireless Wi-Fi and Killer(TM) Wi-Fi in Windows 10 and 11

- [CVE-2021-0162](https://insights.sbomify.com/CVE-2021-0162/): Privilege escalation in Intel(R) PROSet/Wireless Wi-Fi and Killer(TM) Wi-Fi in Windows 10 and 11 (high 8.8)
- [CVE-2021-0163](https://insights.sbomify.com/CVE-2021-0163/): Privilege escalation in Intel(R) PROSet/Wireless Wi-Fi and Killer(TM) Wi-Fi in Windows 10 and 11 (high 8.8)
- [CVE-2021-0066](https://insights.sbomify.com/CVE-2021-0066/): Privilege escalation in Intel(R) PROSet/Wireless Wi-Fi in multiple operating systems and Killer(TM) Wi-Fi in Windows 10 and 11 (high 8.4)
- [CVE-2021-0164](https://insights.sbomify.com/CVE-2021-0164/): Privilege escalation in Intel(R) PROSet/Wireless Wi-Fi in multiple operating systems and Killer(TM) Wi-Fi in Windows 10 and 11 (high 7.8)
- [CVE-2021-0161](https://insights.sbomify.com/CVE-2021-0161/): Privilege escalation in Intel(R) PROSet/Wireless Wi-Fi in multiple operating systems and Killer(TM) Wi-Fi in Windows 10 and 11 (medium 6.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-0177 and fix it if it is affected.

What it is: CVE-2021-0177 is a medium-severity denial of service vulnerability in Intel(R) PROSet/Wireless Wi-Fi and Killer(TM) Wi-Fi in Windows 10 and 11, published on 9 Feb 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-0177 in the wild and no public exploit code.

Affected product: Intel(R) PROSet/Wireless Wi-Fi and Killer(TM) Wi-Fi in Windows 10 and 11. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-0177/ (Markdown: https://insights.sbomify.com/CVE-2021-0177/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-0177
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-0177
- OSV: https://osv.dev/vulnerability/CVE-2021-0177

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-0177/
Summaries are generated and may contain mistakes; the official description above is the record.