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

> Remote attackers can crash the Bluetooth service or execute arbitrary code via a buffer overflow in the Widcomm Bluetooth stack on Windows and mobile devices.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jan 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-85mx-j56c-hfx2

## What is CVE-2006-6908?

CVE-2006-6908 is a critical memory corruption vulnerability in n/a, published on 8 Jan 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in the Bluetooth Stack COM Server in the Widcomm Bluetooth stack, as packaged as Widcomm Stack 3.x and earlier on Windows, Widcomm BTStackServer 1.4.2.10 and 1.3.2.7 on Windows, Widcomm Bluetooth Communication Software 1.4.1.03 on Windows, and the Bluetooth implementation in Windows Mobile or Windows CE on the HP IPAQ 2215 and 5450, allows remote attackers to cause a denial of service (service crash) and possibly execute arbitrary code via unspecified vectors.

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

It affects 3 products.


Products: Broadcom Widcomm Bluetooth, Microsoft Windows Embedded Compact, Microsoft Windows Mobile.

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

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

## Is CVE-2006-6908 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-6905](https://insights.sbomify.com/CVE-2006-6905/): Privilege escalation in n/a (critical 10.0)
- [CVE-2006-6898](https://insights.sbomify.com/CVE-2006-6898/): Information disclosure in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-6908 is a critical memory corruption vulnerability in n/a, published on 8 Jan 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-6908 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-6908/ (Markdown: https://insights.sbomify.com/CVE-2006-6908/index.md)
```

## Sources

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

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