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

> Remote attackers can execute arbitrary commands via shell metacharacters in filenames sent to the Nokia Bluetooth FTP client.

- **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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Jul 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-hrmx-hc55-7cjf

## What is CVE-2005-2277?

CVE-2005-2277 is a critical command injection vulnerability in n/a, published on 15 Jul 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Bluetooth FTP client (BTFTP) in Nokia Affix 2.1.2 and 3.2.0 allows remote attackers to execute arbitrary commands via shell metacharacters in the filename argument of a PUT command.

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

It affects 1 product.


Products: Nokia Affix.

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

Apply the vendor's patch.

## Is CVE-2005-2277 being exploited?

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

Public exploit code:

- Nokia Affix 2.0/2.1/3.x - BTSRV/BTOBEX Remote Command Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2005-2716](https://insights.sbomify.com/CVE-2005-2716/): Command injection in n/a (high 7.5)
- [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-2277 and fix it if it is affected.

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

## Sources

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

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