CVE-2003-0453: traceroute-nanog 6.1.1 allows local users to overwrite unauthorized memory and possibly execute arbitrary code

This month

HIGH 10.0DOWNGRADE

CVE-2003-0453 is a high-severity flaw (CVSS 10.0) affecting traceroute-nanog. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

traceroute-nanog 6.1.1 allows local users to overwrite unauthorized memory and possibly execute arbitrary code via certain "nprobes" and "max_ttl" arguments that cause an integer overflow that is used when allocating memory, which leads to a buffer overflow.

Why this priority

Critical severity

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

Risk facts

CVSS score	10.0 (High)
EPSS exploit chance	2.8% (top 14%)
CISA exploited list	No
Published	2003-08-07
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-08-07 04:00 UTCPublished CVE record published
2026-06-16 22:02 UTCUpdated Record last modified

ehud gavron traceroute-nanog DOWNGRADE

Affected: 6.1.1

Fixed in: no fixed release known

Safe to downgrade to: a release before 6.1.1

1. Check installed version

apt-cache policy traceroute-nanog || rpm -q traceroute-nanog || traceroute-nanog --version

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

apt-cache madison traceroute-nanog sudo apt install traceroute-nanog=<VERSION_BEFORE_6.1.1> sudo apt-mark hold traceroute-nanog

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

dnf --showduplicates list traceroute-nanog sudo dnf downgrade traceroute-nanog-<VERSION_BEFORE_6.1.1> sudo dnf versionlock add traceroute-nanog

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-2003-0453?

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

Is CVE-2003-0453 being exploited?

CVE-2003-0453 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-2003-0453 affect?

CVE-2003-0453 affects traceroute-nanog. Severity is high (CVSS 10.0). traceroute-nanog 6.1.1 allows local users to overwrite unauthorized memory and possibly execute arbitrary code via certain "nprobes" and "max_ttl" arguments that cause an integer overflow that is used when allocating memory, which leads to

How urgent is CVE-2003-0453?

Priority 57/100. Critical severity

References

← Back to latest CVEs