# CVE-2007-0665: Code injection in n/a

> Remote attackers can execute arbitrary commands via format string specifiers in filenames within the SCP module of WS_FTP.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-79gx-39hw-xx5j

## What is CVE-2007-0665?

CVE-2007-0665 is a medium-severity code injection vulnerability in n/a, published on 2 Feb 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Format string vulnerability in the SCP module in Ipswitch WS_FTP 2007 Professional might allow remote attackers to execute arbitrary commands via format string specifiers in the filename, related to the SHELL WS_FTP script command.

## Which versions are affected by CVE-2007-0665?

It affects 1 product.


Products: Ipswitch Ws Ftp Pro.

## How do I fix CVE-2007-0665?

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

## Is CVE-2007-0665 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-0330](https://insights.sbomify.com/CVE-2007-0330/): Memory corruption in n/a (high 7.5)
- [CVE-2002-1851](https://insights.sbomify.com/CVE-2002-1851/): Memory corruption in n/a (high 7.5)
- [CVE-2004-1884](https://insights.sbomify.com/CVE-2004-1884/): Hardcoded credentials in n/a (high 7.5)
- [CVE-1999-1078](https://insights.sbomify.com/CVE-1999-1078/): Weak cryptography in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-0665 and fix it if it is affected.

What it is: CVE-2007-0665 is a medium-severity code injection vulnerability in n/a, published on 2 Feb 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-0665 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-2007-0665/ (Markdown: https://insights.sbomify.com/CVE-2007-0665/index.md)
```

## Sources

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

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