# CVE-2006-0705: Code injection in n/a

> Remote authenticated attackers can execute arbitrary commands via format string vulnerability in SFTP server logging functions.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-2rx6-8ww2-27g3

## What is CVE-2006-0705?

CVE-2006-0705 is a medium-severity code injection vulnerability in n/a, published on 15 Feb 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Format string vulnerability in a logging function as used by various SFTP servers, including (1) AttachmateWRQ Reflection for Secure IT UNIX Server before 6.0.0.9, (2) Reflection for Secure IT Windows Server before 6.0 build 38, (3) F-Secure SSH Server for Windows before 5.3 build 35, (4) F-Secure SSH Server for UNIX 3.0 through 5.0.8, (5) SSH Tectia Server 4.3.6 and earlier and 4.4.0, and (6) SSH Shell Server 3.2.9 and earlier, allows remote authenticated users to execute arbitrary commands via unspecified vectors, involving crafted filenames and the stat command.

Weakness: CWE-134 (Use of Externally-Controlled Format String)

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

It affects 2 products.


Products: Attachmatewrq Reflection for Secure It Server, F-Secure F-Secure Ssh Server.

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

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

## Is CVE-2006-0705 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2006-0705 is a medium-severity code injection vulnerability in n/a, published on 15 Feb 2006. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-0705 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-0705/ (Markdown: https://insights.sbomify.com/CVE-2006-0705/index.md)
```

## Sources

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

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