How severe is GHSA-rjvj-673q-4hfw?

No CVSS score has been assigned to GHSA-rjvj-673q-4hfw yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-rjvj-673q-4hfw?

GHSA-rjvj-673q-4hfw affects the following packages: traceroute (npm). Ecosystems affected: npm.

How do I fix GHSA-rjvj-673q-4hfw?

The records we use list no patched version of traceroute for GHSA-rjvj-673q-4hfw. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect GHSA-rjvj-673q-4hfw in my npm dependencies?

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.

How do I mitigate GHSA-rjvj-673q-4hfw if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is GHSA-rjvj-673q-4hfw actively exploited in the wild?

No public exploit code has been indexed for GHSA-rjvj-673q-4hfw yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-rjvj-673q-4hfw published, and has it been updated?

GHSA-rjvj-673q-4hfw was published on September 4, 2020 and was last updated on October 4, 2021. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Command Injection in tracerouteGHSA-rjvj-673q-4hfw

GHSA-rjvj-673q-4hfw is a remote code execution vulnerability in traceroute. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

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

367downloads / 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

Ecosystem	Package	Vulnerable range	Fix
📦npm	`traceroute`	≥ 0.0.0	No fix

Detection & mitigation playbook

Open-source dependency

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.
Remediation status
The records we use list no patched version of traceroute for GHSA-rjvj-673q-4hfw. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

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?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works