# CVE-2009-4053: Path traversal in n/a

> Authenticated attackers can create arbitrary directories and files via path traversal in Home FTP Server, allowing unauthorized file system modifications.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 23 Nov 2009
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-gchh-gcff-w82w

## What is CVE-2009-4053?

CVE-2009-4053 is a medium-severity path traversal vulnerability in n/a, published on 23 Nov 2009. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple directory traversal vulnerabilities in Home FTP Server 1.10.1.139 allow remote authenticated users to (1) create arbitrary directories via directory traversal sequences in an MKD command or (2) create files with any contents in arbitrary directories via directory traversal sequences in a file upload request.  NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Home Ftp Server Project Home Ftp Server.

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

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

## Is CVE-2009-4053 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-4053 exists.

Public exploit code:

- Home FTP Server - 'MKD' Directory Traversal (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-4053 is a medium-severity path traversal vulnerability in n/a, published on 23 Nov 2009. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-4053 exists.

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-4053/ (Markdown: https://insights.sbomify.com/CVE-2009-4053/index.md)
```

## Sources

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

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