# CVE-2006-2403: Memory corruption in n/a

> Remote attackers can execute arbitrary commands via a buffer overflow in the FileZilla FTP client.

- **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:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 16 May 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-w7x9-8grp-c8p2

## What is CVE-2006-2403?

CVE-2006-2403 is a high-severity memory corruption vulnerability in n/a, published on 16 May 2006. An attacker can exploit it over the internet without logging in.

### Official description

Buffer overflow in FileZilla before 2.2.23 allows remote attackers to execute arbitrary commands via unknown attack vectors.

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

It affects 1 product.


Products: Filezilla Filezilla.

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

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

## Is CVE-2006-2403 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-2318](https://insights.sbomify.com/CVE-2007-2318/): Memory corruption in n/a (critical 9.3)
- [CVE-2007-0315](https://insights.sbomify.com/CVE-2007-0315/): Memory corruption in n/a (critical 9.3)
- [CVE-2007-0317](https://insights.sbomify.com/CVE-2007-0317/): Other in n/a (high 7.5)
- [CVE-2005-2898](https://insights.sbomify.com/CVE-2005-2898/): Weak cryptography in n/a (medium 4.6)
- [CVE-2006-6564](https://insights.sbomify.com/CVE-2006-6564/): Null dereference in n/a (medium 4.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-2403 is a high-severity memory corruption vulnerability in n/a, published on 16 May 2006. An attacker can exploit it over the internet without logging in.
Exploitation: There is no known exploitation of CVE-2006-2403 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-2403/ (Markdown: https://insights.sbomify.com/CVE-2006-2403/index.md)
```

## Sources

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

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