# CVE-2008-2161: Memory corruption in n/a

> Remote attackers can execute arbitrary code on TFTP Server via a buffer overflow in error packet handling.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 May 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-fxvv-792x-8mjp

## What is CVE-2008-2161?

CVE-2008-2161 is a critical memory corruption vulnerability in n/a, published on 12 May 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in TFTP Server SP 1.4 and 1.5 on Windows, and possibly other versions, allows remote attackers to execute arbitrary code via a long TFTP error packet.  NOTE: some of these details are obtained from third party information.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2008-2161?

It affects 1 product.


Products: Tftp Tftp Server Sp.

## How do I fix CVE-2008-2161?

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

## Is CVE-2008-2161 being exploited?

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

Public exploit code:

- TFTP Server for Windows 1.4 - ST Remote BSS Overflow (exploitdb)
- OpenTFTP SP 1.4 Error Packet Overflow (metasploit)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-2161 and fix it if it is affected.

What it is: CVE-2008-2161 is a critical memory corruption vulnerability in n/a, published on 12 May 2008. 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-2008-2161 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-2008-2161/ (Markdown: https://insights.sbomify.com/CVE-2008-2161/index.md)
```

## Sources

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

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