Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm
Not in CISA KEV

GHSA-rjvj-673q-4hfw traceroute

GHSA-rjvj-673q-4hfw is a remote code execution vulnerability in traceroute. No vendor fix is recorded yet; mitigation options are listed below.

Command Injection in traceroute

Published
Sep 4, 2020
Updated
Oct 4, 2021
Affected
1 pkg
Patched
None yet
Exploits
None indexed
Exploitation data as of Oct 4, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

4other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
traceroutenpm
329downloads / week

Description

All versions of traceroute are vulnerable to Command Injection. The package fails to sanitize input and passes it directly to an exec call, which may allow attackers to execute arbitrary code in the system. The trace function is vulnerable and can be abused if the host value is controlled by an attacker.

Recommendation

No fix is currently available. Consider using an alternative package until a fix is made available.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
📦npmtraceroute0.0.0No fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for traceroute, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Remediation status

    No patched version of traceroute has shipped for GHSA-rjvj-673q-4hfw yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-rjvj-673q-4hfw can be triaged on real exposure rather than presence alone.

Tailored to GHSA-rjvj-673q-4hfw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

All versions of `traceroute` are vulnerable to Command Injection. The package fails to sanitize input and passes it directly to an `exec` call, which may allow attackers to execute arbitrary code in the system. The `trace` function is vulnerable and can be abused if the `host` value is controlled by an attacker. ## Recommendation No fix is currently available. Consider using an alternative package until a fix is made available.
O3 Security · Impact-Aware SCA

Is GHSA-rjvj-673q-4hfw in your dependencies?

O3 Security finds GHSA-rjvj-673q-4hfw across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-rjvj-673q-4hfw: traceroute RCE | O3 Security