# CVE-2009-3478: Command injection in n/a

> Remote attackers can manipulate file operations in FireFTP by injecting double quotes into filenames, causing victims to alter, delete, or move unintended files.

- **Severity:** Medium 6.0 (`AV:N/AC:M/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Sep 2009
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-6jvf-r79g-h3f2

## What is CVE-2009-3478?

CVE-2009-3478 is a medium-severity command injection vulnerability in n/a, published on 29 Sep 2009. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Argument injection vulnerability in (1) src/content/js/connection/sftp.js and (2) src/content/js/connection/controlSocket.js.in in FireFTP Extension 1.0.5 for Firefox allows remote authenticated SFTP users to cause victims to alter permissions, delete, download, or move the wrong file via a filename containing " (double quotes), which is not properly filtered or encoded when FireFTP constructs the command to send to psftp.exe.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2009-3478?

It affects 1 product.


Products: Nightlight Fireftp.

## How do I fix CVE-2009-3478?

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

## Is CVE-2009-3478 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-3478 and fix it if it is affected.

What it is: CVE-2009-3478 is a medium-severity command injection vulnerability in n/a, published on 29 Sep 2009. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2009-3478 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-2009-3478/ (Markdown: https://insights.sbomify.com/CVE-2009-3478/index.md)
```

## Sources

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

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