Command Injection in traceroute
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 software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| npm package | traceroute | >= 0.0.0 | no fix |
References
- Weakness (CWE)
CWE-77- Platform
- npm
- Package
traceroute- Disclosed
- 04.09.2020
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-rjvj-673q-4hfw - CC BY 4.0
Vulnerability history: traceroute
All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 2
- First → latest
- 09.2020 05.2022
- Without a fix
- 2
- Exploited in attacks
- 0
Severity breakdown
- Critical 2
Disclosures per year
- 2020: 1
- 2021: 0
- 2022: 1
- 2023: 0
- 2024: 0
- 2025: 0
- 2026: 0
-
Command Injection in traceroute this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.