# CVE-2013-6809: Other in n/a

> A format string vulnerability in the Tftpd32 client allows remote servers to cause a crash or execute arbitrary code via malicious file names.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Dec 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-3795-4m6r-47rj

## What is CVE-2013-6809?

CVE-2013-6809 is a medium-severity vulnerability in n/a, published on 13 Dec 2013. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Format string vulnerability in the client in Tftpd32 before 4.50 allows remote servers to cause a denial of service (crash) or possibly execute arbitrary code via format string specifiers in the Remote File field.

Weakness: CWE-134 (Use of Externally-Controlled Format String)

## Which versions are affected by CVE-2013-6809?

It affects 1 product.


Products: Philippe Jounin Tftpd32.

## How do I fix CVE-2013-6809?

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

## Is CVE-2013-6809 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-4882](https://insights.sbomify.com/CVE-2005-4882/): Denial of service in n/a (medium 5.0)
- [CVE-2006-6141](https://insights.sbomify.com/CVE-2006-6141/): Memory corruption in n/a (medium 5.0)
- [CVE-2006-0328](https://insights.sbomify.com/CVE-2006-0328/): Memory corruption in n/a (medium 5.0)
- [CVE-2005-4883](https://insights.sbomify.com/CVE-2005-4883/): Race condition in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-6809 and fix it if it is affected.

What it is: CVE-2013-6809 is a medium-severity vulnerability in n/a, published on 13 Dec 2013. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2013-6809 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-2013-6809/ (Markdown: https://insights.sbomify.com/CVE-2013-6809/index.md)
```

## Sources

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

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