# CVE-2002-2396: Memory corruption in n/a

> Local attackers can execute arbitrary code with elevated privileges via a buffer overflow in the atftp TFTP server when setuid or setgid is enabled.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Nov 2007
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-76v7-f945-pwp9

## What is CVE-2002-2396?

CVE-2002-2396 is a high-severity memory corruption vulnerability in n/a, published on 1 Nov 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Buffer overflow in Advanced TFTP (atftp) 0.5 and 0.6, if installed setuid or setgid, may allow local users to execute arbitrary code via a long argument to the -g option.

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

## Which versions are affected by CVE-2002-2396?

It affects 1 product.


Products: Remi Lefebvre Advanced Tftp.

## How do I fix CVE-2002-2396?

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

## Is CVE-2002-2396 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-2396 and fix it if it is affected.

What it is: CVE-2002-2396 is a high-severity memory corruption vulnerability in n/a, published on 1 Nov 2007. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2002-2396 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-2002-2396/ (Markdown: https://insights.sbomify.com/CVE-2002-2396/index.md)
```

## Sources

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

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