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

> Remote attackers can execute arbitrary commands via shell metacharacters in Bluetooth device names, affecting Nokia Affix Bluetooth stacks.

- **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:** 29 Aug 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DSA-796-1, GHSA-ccx2-62m5-vf68

## What is CVE-2005-2716?

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

### Official description

The event_pin_code_request function in the btsrv daemon (btsrv.c) in Nokia Affix 2.1.2 and 3.2.0 allows remote attackers to execute arbitrary commands via shell metacharacters in a Bluetooth device name.

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

It affects 1 product.


Products: Nokia Affix.

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

Apply the vendor's patch.

## Is CVE-2005-2716 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-2277](https://insights.sbomify.com/CVE-2005-2277/): Command injection in n/a (critical 10.0)
- [CVE-2005-2250](https://insights.sbomify.com/CVE-2005-2250/): Memory corruption in n/a (high 7.5)
- [CVE-2005-1294](https://insights.sbomify.com/CVE-2005-1294/): Integer overflow in n/a (high 7.2)

## Fix prompt for AI coding agents

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

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

## Sources

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

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