# CVE-2002-1387: Integer overflow in n/a

> Local attackers can exploit an integer overflow in traceroute-nanog to overwrite memory, potentially leading to arbitrary code execution or privilege escalation.

- **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-4395-98rh-2625

## What is CVE-2002-1387?

CVE-2002-1387 is a medium-severity 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

The spray mode in traceroute-nanog (aka traceroute-ng) may allow local users to overwrite arbitrary memory locations via an array index overflow using the nprobes (number of probes) argument.

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

It affects 1 product.


Products: Ehud Gavron Tracesroute.

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

Apply the vendor's patch.

## Is CVE-2002-1387 being exploited?

There is no known exploitation of CVE-2002-1387 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-1386](https://insights.sbomify.com/CVE-2002-1386/): Memory corruption in n/a (medium 4.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-1387 is a medium-severity 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-1387 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-1387/ (Markdown: https://insights.sbomify.com/CVE-2002-1387/index.md)
```

## Sources

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

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