# CVE-2005-2547: Command injection in n/a

> Remote attackers can execute arbitrary commands via shell metacharacters in Bluetooth device names, affecting BlueZ implementations.

- **Severity:** High 7.5 (`AV:N/AC:L/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:** Yes
- **Published:** 12 Aug 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DSA-782-1, DTSA-9-1, GHSA-35vq-2ggj-6fwg

## What is CVE-2005-2547?

CVE-2005-2547 is a high-severity command injection vulnerability in n/a, published on 12 Aug 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

security.c in hcid for BlueZ 2.16, 2.17, and 2.18 allows remote attackers to execute arbitrary commands via shell metacharacters in the Bluetooth device name when invoking the PIN helper.

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

It affects 1 product.


Products: Bluez Project Bluez.

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

Apply the vendor's patch.

## Is CVE-2005-2547 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-9918](https://insights.sbomify.com/CVE-2016-9918/): Denial of service in n/a (high 7.5)
- [CVE-2006-6899](https://insights.sbomify.com/CVE-2006-6899/): Missing authorization in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-2547 is a high-severity command injection vulnerability in n/a, published on 12 Aug 2005. 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-2005-2547 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-2005-2547/ (Markdown: https://insights.sbomify.com/CVE-2005-2547/index.md)
```

## Sources

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

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