# CVE-2019-11151: Memory corruption in Intel(R) WIFI Drivers and Intel(R) PROSet/Wireless WiFi Software extension DLL

> Privileged local attackers can exploit memory corruption in Intel WiFi drivers to escalate privileges, cause denial of service, or disclose information.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Nov 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-52qr-28j9-p9j3

## What is CVE-2019-11151?

CVE-2019-11151 is a high-severity memory corruption vulnerability in Intel(R) WIFI Drivers and Intel(R) PROSet/Wireless WiFi Software extension DLL, published on 14 Nov 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Memory corruption issues in Intel(R) WIFI Drivers before version 21.40 may allow a privileged user to potentially enable escalation of privilege, denial of service, and information disclosure via local access.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2019-11151?

It affects 13 products.


Products: Intel Dual Band Wireless-Ac 3165 Firmware, Intel Dual Band Wireless-Ac 3168 Firmware, Intel Dual Band Wireless-Ac 7265 Firmware, Intel Dual Band Wireless-Ac 8260 Firmware, Intel Dual Band Wireless-Ac 8265 Firmware, Intel Dual Band Wireless-N 7265 Firmware, Intel Wi-Fi 6 Ax200 Firmware, Intel Wi-Fi 6 Ax201 Firmware, Intel Wireless-Ac 9260 Firmware, Intel Wireless-Ac 9461 Firmware, Intel Wireless-Ac 9462 Firmware, Intel Wireless-Ac 9560 Firmware, Intel Wireless-N 7265 Firmware.

## How do I fix CVE-2019-11151?

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

## Is CVE-2019-11151 being exploited?

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

## Other vulnerabilities in Intel(R) WIFI Drivers and Intel(R) PROSet/Wireless WiFi Software extension DLL

- [CVE-2020-12321](https://insights.sbomify.com/CVE-2020-12321/): Privilege escalation in Intel(R) Wireless Bluetooth(R) (high 8.8)
- [CVE-2019-11152](https://insights.sbomify.com/CVE-2019-11152/): Memory corruption in Intel(R) WIFI Drivers and Intel(R) PROSet/Wireless WiFi Software extension DLL (high 8.8)
- [CVE-2021-33847](https://insights.sbomify.com/CVE-2021-33847/): Memory corruption in Intel(R) Wireless Bluetooth(R) and Killer(TM) Bluetooth(R) products (high 7.8)
- [CVE-2021-23179](https://insights.sbomify.com/CVE-2021-23179/): Information disclosure in Intel(R) Wireless Bluetooth(R) and Killer(TM) Bluetooth(R) products (high 7.1)
- [CVE-2022-28667](https://insights.sbomify.com/CVE-2022-28667/): Memory corruption in Intel(R) PROSet/Wireless WiFi software (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-11151 and fix it if it is affected.

What it is: CVE-2019-11151 is a high-severity memory corruption vulnerability in Intel(R) WIFI Drivers and Intel(R) PROSet/Wireless WiFi Software extension DLL, published on 14 Nov 2019. 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-2019-11151 in the wild and no public exploit code.

Affected product: Intel(R) WIFI Drivers and Intel(R) PROSet/Wireless WiFi Software extension DLL. 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-2019-11151/ (Markdown: https://insights.sbomify.com/CVE-2019-11151/index.md)
```

## Sources

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

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