# CVE-2006-6651: Race condition in n/a

> Remote attackers can execute arbitrary code via crafted beacon frames exploiting a race condition in the Intel 2200BG wireless driver.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **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:** 20 Dec 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-x86m-wjrw-6w52

## What is CVE-2006-6651?

CVE-2006-6651 is a medium-severity vulnerability in n/a, published on 20 Dec 2006. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Race condition in W29N51.SYS in the Intel 2200BG wireless driver 9.0.3.9 allows remote attackers to cause memory corruption and execute arbitrary code via a series of crafted beacon frames.  NOTE: some details are obtained solely from third party information.

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

It affects 1 product.


Products: Intel 2200bg Proset Wireless.

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

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

## Is CVE-2006-6651 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-6651 exists.

Public exploit code:

- Intel 2200BG 802.11 - Beacon frame Kernel Memory Corruption (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-0686](https://insights.sbomify.com/CVE-2007-0686/): Memory corruption in n/a (high 7.1)
- [CVE-2006-3992](https://insights.sbomify.com/CVE-2006-3992/): Memory corruption in n/a (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-6651 is a medium-severity vulnerability in n/a, published on 20 Dec 2006. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-6651 exists.

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-6651/ (Markdown: https://insights.sbomify.com/CVE-2006-6651/index.md)
```

## Sources

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

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