# CVE-2006-5949: Path traversal in n/a

> Remote attackers can create arbitrary directories on ALTools ALFTP FTP Server via path traversal in MKD requests.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Nov 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-h4mp-w8gj-64qx

## What is CVE-2006-5949?

CVE-2006-5949 is a medium-severity path traversal vulnerability in n/a, published on 17 Nov 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in ALTools ALFTP FTP Server 4.1 beta 1, and possibly earlier, allows remote attackers to create arbitrary directories via directory traversal sequences in a MKD request.  NOTE: the provenance of this information is unknown; details are obtained from third party sources.

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

It affects 1 product.


Products: Altools Alftp Ftp Server.

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

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

## Is CVE-2006-5949 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-5950](https://insights.sbomify.com/CVE-2006-5950/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-5949 is a medium-severity path traversal vulnerability in n/a, published on 17 Nov 2006. 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-2006-5949 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-5949/ (Markdown: https://insights.sbomify.com/CVE-2006-5949/index.md)
```

## Sources

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

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