# CVE-2016-8104: Memory corruption in Intel PROSet/Wireless Software and Drivers

> A local attacker can trigger a buffer overflow in Intel PROSet/Wireless Software to crash the iframewrk.exe process, causing a denial of service.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:** 8 Dec 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-cxpv-4qr3-6ggq

## What is CVE-2016-8104?

CVE-2016-8104 is a medium-severity memory corruption vulnerability in Intel PROSet/Wireless Software and Drivers, published on 8 Dec 2016. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Buffer overflow in Intel PROSet/Wireless Software and Drivers in versions before 19.20.3 allows a local user to crash iframewrk.exe causing a potential denial of service.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2016-8104?

It affects 1 product.


Products: Intel Proset\/Wireless Software and Drivers.

## How do I fix CVE-2016-8104?

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

## Is CVE-2016-8104 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-8104 and fix it if it is affected.

What it is: CVE-2016-8104 is a medium-severity memory corruption vulnerability in Intel PROSet/Wireless Software and Drivers, published on 8 Dec 2016. 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-2016-8104 in the wild and no public exploit code.

Affected product: Intel PROSet/Wireless Software and Drivers. 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-2016-8104/ (Markdown: https://insights.sbomify.com/CVE-2016-8104/index.md)
```

## Sources

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

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