# CVE-2006-6898: Information disclosure in n/a

> Remote attackers can eavesdrop on and record Bluetooth conversations via the Widcomm Bluetooth for Windows software.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:C/I:N/A:N`)
- **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:** 8 Jan 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8wvq-229q-3j9g

## What is CVE-2006-6898?

CVE-2006-6898 is a high-severity vulnerability in n/a, published on 8 Jan 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Widcomm Bluetooth for Windows (BTW) before 4.0.1.1500 allows remote attackers to listen to and record conversations, aka the CarWhisperer attack.

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

It affects 1 product.


Products: Broadcom Widcomm Bluetooth.

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

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

## Is CVE-2006-6898 being exploited?

There is no known exploitation of CVE-2006-6898 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-6908](https://insights.sbomify.com/CVE-2006-6908/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-6898 is a high-severity vulnerability in n/a, published on 8 Jan 2007. 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-6898 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-6898/ (Markdown: https://insights.sbomify.com/CVE-2006-6898/index.md)
```

## Sources

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

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