# CVE-2005-4417: Misconfiguration in n/a

> Remote attackers can eavesdrop via microphone or send audio due to null authentication in default Bluetooth configurations.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/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:** 20 Dec 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-h84p-p4v5-gw25

## What is CVE-2005-4417?

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

### Official description

The default configuration of Widcomm Bluetooth for Windows (BTW) 4.0.1.1500 and earlier, as installed on Belkin Bluetooth Software 1.4.2 Build 10 and ANYCOM Blue USB-130-250 Software 4.0.1.1500, and possibly other devices, sets null Authentication and Authorization values, which allows remote attackers to send arbitrary audio and possibly eavesdrop using the microphone via the Hands Free Audio Gateway and Headset profile.

## Which versions are affected by CVE-2005-4417?

It affects 3 products.


Products: Anycom Blue Usb-130-250 Software, Belkin Bluetooth Software, Widcomm Bluetooth for Windows.

## How do I fix CVE-2005-4417?

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

## Is CVE-2005-4417 being exploited?

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

Public exploit code:

- WIDCOMM Bluetooth Software < 3.0 - Remote Buffer Overflow (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-4417 and fix it if it is affected.

What it is: CVE-2005-4417 is a medium-severity vulnerability in n/a, published on 20 Dec 2005. 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-2005-4417 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-2005-4417/ (Markdown: https://insights.sbomify.com/CVE-2005-4417/index.md)
```

## Sources

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

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