# CVE-2012-6664: Path traversal in n/a

> Remote attackers can read or write arbitrary files on the TFTP server via directory traversal in get or put commands.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 21 Jun 2024
- **Updated:** 15 Sep 2024
- **Also known as:** GHSA-c8f7-vvrw-73c7

## What is CVE-2012-6664?

CVE-2012-6664 is a critical path traversal vulnerability in n/a, published on 21 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple directory traversal vulnerabilities in the TFTP Server in Distinct Intranet Servers 3.10 and earlier allow remote attackers to read or write arbitrary files via a .. (dot dot) in the (1) get or (2) put commands.

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

## Which versions are affected by CVE-2012-6664?


## How do I fix CVE-2012-6664?

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

## Is CVE-2012-6664 being exploited?

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

Public exploit code:

- Distinct TFTP 3.10 - Writable Directory Traversal Execution (Metasploit) (exploitdb)
- Distinct TFTP 3.10 Writable Directory Traversal Execution (metasploit)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-6664 and fix it if it is affected.

What it is: CVE-2012-6664 is a critical path traversal vulnerability in n/a, published on 21 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-6664 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-2012-6664/ (Markdown: https://insights.sbomify.com/CVE-2012-6664/index.md)
```

## Sources

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

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