PatchTheCVEtracesroute vulnerabilities and fixes
Recent CVEs affecting tracesroute, with upgrade or downgrade steps. 4 tracked.
tracesroute has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2003-01-02. Highest priority: CVE-2002-1364 (score 49/100).
- CVE-2002-1387 MEDIUM 4.6 DOWNGRADE The spray mode in traceroute-nanog (aka traceroute-ng) may allow local users to overwrite arbitrary memory loc
- 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
FAQ
How do I fix tracesroute vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is tracesroute being exploited right now?
None of the tracked tracesroute CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which tracesroute CVE should I patch first?
CVE-2002-1364 currently ranks highest (49/100): Buffer overflow in the get_origin function in traceroute-nanog allows attackers to execute arbitrary code via .