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

> Authenticated attackers can trigger a buffer overflow in Gene6 FTP Server via long MKD or XMKD arguments, causing crashes or arbitrary code execution.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/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:** 4 May 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wwrm-hmmc-45q7

## What is CVE-2006-2172?

CVE-2006-2172 is a high-severity memory corruption vulnerability in n/a, published on 4 May 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Buffer overflow in Gene6 FTP Server 3.1.0 allows remote authenticated attackers to cause a denial of service (crash) and possibly execute arbitrary code via a long argument to (1) MKD or (2) XMKD, as demonstrated by the Infigo FTPStress Fuzzer.

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

It affects 1 product.


Products: Gene6 G6 Ftp Server.

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

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

## Is CVE-2006-2172 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2001-0263](https://insights.sbomify.com/CVE-2001-0263/): Path traversal in n/a (high 7.5)
- [CVE-1999-1519](https://insights.sbomify.com/CVE-1999-1519/): Denial of service in n/a (medium 5.0)
- [CVE-2001-0264](https://insights.sbomify.com/CVE-2001-0264/): Information disclosure in n/a (medium 5.0)
- [CVE-2005-0690](https://insights.sbomify.com/CVE-2005-0690/): Missing authorization in n/a (low 2.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-2172 is a high-severity memory corruption vulnerability in n/a, published on 4 May 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-2172 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-2172/ (Markdown: https://insights.sbomify.com/CVE-2006-2172/index.md)
```

## Sources

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

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