CVE-2002-1387

NONECVSS 0.0

0.0

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.

CVSS v3: —
EG Score: —
EPSS: 22.2%
KEV: Not listed

Published

January 2, 2003

Last Modified

April 16, 2026

References (2)

cve@mitrehttp://marc.info/?l=bugtraq&m=103849968732634&w=2
af854a3a-2127-422b-91ae-364da2661108http://marc.info/?l=bugtraq&m=103849968732634&w=2

Data Freshness Timeline

(refreshed 12× in last 7d / 17× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-05-29 13:40 UTCepss_batch
2026-05-29 13:40 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-27 13:37 UTCepss_batch
2026-05-26 13:41 UTCepss_batch
2026-05-26 13:41 UTCepss_batch
2026-05-26 07:16 UTCepss_batch
2026-05-26 07:16 UTCepss_batch
2026-05-24 16:42 UTCepss_batch
2026-05-22 21:15 UTCepss_batch
2026-05-20 22:36 UTCepss_batch
2026-05-20 11:20 UTCepss_batch
2026-05-20 11:20 UTCepss_batch
2026-05-18 21:29 UTCepss_batch
2026-05-18 21:29 UTCepss_batch

Frequently asked(4)

What is CVE-2002-1387?

CVE-2002-1387 is a none vulnerability published on January 2, 2003. 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.

When was CVE-2002-1387 disclosed?

CVE-2002-1387 was first published in the National Vulnerability Database on January 2, 2003, with the most recent update on April 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2002-1387 actively exploited?

CVE-2002-1387 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 22.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

How do I remediate CVE-2002-1387?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2002-1387, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2002-1387

Explore →

Is Your Infrastructure Affected by CVE-2002-1387?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2002-1387

📅 Published

🔄 Last Modified

🔗 References (2)