# CVE-2007-0686: Memory corruption in n/a

> Remote attackers can crash the system via crafted disassociation packets due to memory corruption in the Intel 2200BG wireless driver.

- **Severity:** High 7.1 (`AV:N/AC:M/Au:N/C:N/I:N/A:C`)
- **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:** 3 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wwqj-cvrv-7w8x

## What is CVE-2007-0686?

CVE-2007-0686 is a high-severity memory corruption vulnerability in n/a, published on 3 Feb 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Intel 2200BG 802.11 Wireless Mini-PCI driver 9.0.3.9 (w29n51.sys) allows remote attackers to cause a denial of service (system crash) via crafted disassociation packets, which triggers memory corruption of "internal kernel structures," a different vulnerability than CVE-2006-6651.  NOTE: this issue might overlap CVE-2006-3992.

## Which versions are affected by CVE-2007-0686?

It affects 1 product.


Products: Intel 2200bg Proset Wireless.

## How do I fix CVE-2007-0686?

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

## Is CVE-2007-0686 being exploited?

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

Public exploit code:

- Intel 2200BG 802.11 - disassociation packet Kernel Memory Corruption (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-6651](https://insights.sbomify.com/CVE-2006-6651/): Race condition in n/a (medium 6.8)
- [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-2007-0686 and fix it if it is affected.

What it is: CVE-2007-0686 is a high-severity memory corruption vulnerability in n/a, published on 3 Feb 2007. 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-2007-0686 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-2007-0686/ (Markdown: https://insights.sbomify.com/CVE-2007-0686/index.md)
```

## Sources

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

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