CVE-2002-1387: The spray mode in traceroute-nanog (aka traceroute-ng) may allow local users to overwrite arbitrary memory loc

Routine

MEDIUM 4.6DOWNGRADE

CVE-2002-1387 is a medium-severity flaw (CVSS 4.6) affecting tracesroute. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

No elevated risk signals yet

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	4.6 (Medium)
EPSS exploit chance	0.3% (top 75%)
CISA exploited list	No
Published	2003-01-02
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: ehud gavron

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2003-01-02 05:00 UTCPublished CVE record published
2026-06-16 21:59 UTCUpdated Record last modified

ehud gavron tracesroute DOWNGRADE

Affected: 6.0 · 6.1 · 6.1.1

Fixed in: no fixed release known

Safe to downgrade to: a release before 6.0

1. Check installed version

apt-cache policy tracesroute || rpm -q tracesroute || tracesroute --version

2. No fixed release: DOWNGRADE to a release before 6.0 (Debian / Ubuntu)

apt-cache madison tracesroute sudo apt install tracesroute=<VERSION_BEFORE_6.0> sudo apt-mark hold tracesroute

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list tracesroute sudo dnf downgrade tracesroute-<VERSION_BEFORE_6.0> sudo dnf versionlock add tracesroute

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2002-1387?

tracesroute: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2002-1387 being exploited?

CVE-2002-1387 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2002-1387 affect?

CVE-2002-1387 affects tracesroute. Severity is medium (CVSS 4.6). 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.

How urgent is CVE-2002-1387?

Priority 22/100. No elevated risk signals yet.

Related CVEs

CVE-2002-1386 MEDIUM 4.6 DOWNGRADE Buffer overflow in traceroute-nanog (aka traceroute-ng) may allow local users to execute arbitrary code via a
CVE-2002-1364 HIGH 7.2 DOWNGRADE Buffer overflow in the get_origin function in traceroute-nanog allows attackers to execute arbitrary code via
CVE-2002-1051 MEDIUM 4.6 DOWNGRADE Format string vulnerability in TrACESroute 6.0 GOLD (aka NANOG traceroute) allows local users to execute arbit

References

← Back to latest CVEs