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

> Local attackers can execute arbitrary code via a buffer overflow in traceroute-nanog by providing a long hostname argument.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Dec 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-77px-37x7-938j

## What is CVE-2002-1386?

CVE-2002-1386 is a medium-severity memory corruption vulnerability in n/a, published on 31 Dec 2002. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Buffer overflow in traceroute-nanog (aka traceroute-ng) may allow local users to execute arbitrary code via a long hostname argument.

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

It affects 1 product.


Products: Ehud Gavron Tracesroute.

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

Apply the vendor's patch.

## Is CVE-2002-1386 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-1364](https://insights.sbomify.com/CVE-2002-1364/): Memory corruption in n/a (high 7.2)
- [CVE-2002-1051](https://insights.sbomify.com/CVE-2002-1051/): Code injection in n/a (medium 4.6)
- [CVE-2002-1387](https://insights.sbomify.com/CVE-2002-1387/): Integer overflow in n/a (medium 4.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-1386 is a medium-severity memory corruption vulnerability in n/a, published on 31 Dec 2002. 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-1386 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-1386/ (Markdown: https://insights.sbomify.com/CVE-2002-1386/index.md)
```

## Sources

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

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