CVE-2023-46316: In buc Traceroute 2.0.12 through 2.1.2 before 2.1.3, the wrapper scripts do not properly parse command lines.

Routine

MEDIUM 5.5WATCHLISTUPGRADEMITIGATE

CVE-2023-46316 is a medium-severity flaw (CVSS 5.5) affecting traceroute, debian linux. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

In buc Traceroute 2.0.12 through 2.1.2 before 2.1.3, the wrapper scripts do not properly parse command lines.

Why this priority

On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	5.5 (Medium)
Attack vector	Local
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.4% (top 67%)
CISA exploited list	No
Weakness	CWE-234
Published	2023-10-25
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: buc · debian

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

Am I affected?

Timeline

2023-10-25 18:17 UTCPublished CVE record published
2026-06-17 06:30 UTCUpdated Record last modified

buc traceroute UPGRADE

Affected: >= 2.0.12 and < 2.1.3

Fixed in: 2.1.3

Safe to downgrade to: a release before 2.0.12

1. Check installed version

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

2. UPGRADE to 2.1.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade traceroute

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade traceroute

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 2.0.12 (Debian / Ubuntu)

apt-cache madison traceroute sudo apt install traceroute=<VERSION_BEFORE_2.0.12> sudo apt-mark hold traceroute

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list traceroute sudo dnf downgrade traceroute-<VERSION_BEFORE_2.0.12> sudo dnf versionlock add traceroute

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.

debian debian linux MITIGATE

Affected: 10.0 · 11.0 · 12.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 10.0

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

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-2023-46316?

traceroute: upgrade to 2.1.3; debian linux: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2023-46316 being exploited?

CVE-2023-46316 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-2023-46316 affect?

CVE-2023-46316 affects traceroute, debian linux. Severity is medium (CVSS 5.5). In buc Traceroute 2.0.12 through 2.1.2 before 2.1.3, the wrapper scripts do not properly parse command lines.

How urgent is CVE-2023-46316?

Priority 32/100. On your watchlist

Software pages

Debian vulnerabilities

Related CVEs

CVE-2018-21268 CRITICAL 10.0 UPGRADE The traceroute (aka node-traceroute) package through 1.0.0 for Node.js allows remote command injection via the

References

← Back to latest CVEs