# CVE-2006-4022: Memory corruption in n/a

> Local attackers can execute arbitrary code and escalate privileges by sending crafted frames to the Intel 2100 PRO/Wireless driver.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** 9 Aug 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-x67w-2fr6-2264

## What is CVE-2006-4022?

CVE-2006-4022 is a medium-severity memory corruption vulnerability in n/a, published on 9 Aug 2006. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Intel 2100 PRO/Wireless Network Connection driver PROSet before 7.1.4.6 allows local users to corrupt memory and execute code via "requests for capabilities from higher-level protocol drivers or user-level applications" involving crafted frames, a different issue than CVE-2006-3992.

## Which versions are affected by CVE-2006-4022?

It affects 1 product.


Products: Intel 2100 Proset Wireless.

## How do I fix CVE-2006-4022?

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

## Is CVE-2006-4022 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-4022 and fix it if it is affected.

What it is: CVE-2006-4022 is a medium-severity memory corruption vulnerability in n/a, published on 9 Aug 2006. 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-2006-4022 in the wild and no public exploit code.

Affected product: n/a. 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-2006-4022/ (Markdown: https://insights.sbomify.com/CVE-2006-4022/index.md)
```

## Sources

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

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