# CVE-2018-21268: Node-Traceroute RCE Vulnerability

> Remote attackers can execute arbitrary OS commands via the host parameter in the node-traceroute library due to unsafe use of Child.exec().

- **Severity:** Critical 10.0 (`CVSS:3.1/AC:L/AV:N/A:L/C:H/I:H/PR:N/S:C/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jun 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-8j9v-qhp4-wv55

## What is CVE-2018-21268?

CVE-2018-21268 is a critical command injection vulnerability in n/a, published on 25 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The traceroute (aka node-traceroute) package through 1.0.0 for Node.js allows remote command injection via the host parameter. This occurs because the Child.exec() method, which is considered to be not entirely safe, is used. In particular, an OS command can be placed after a newline character.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2018-21268?

2 open source packages ship an affected version, including traceroute. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `traceroute` | npm | All versions to 1.0.0 | None |
| `traceroute` | npm | All versions to 1.0.0 | None |

Products: Traceroute Project Traceroute.

## How do I fix CVE-2018-21268?

No fix has been published for CVE-2018-21268 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-21268 being exploited?

There is no known exploitation of CVE-2018-21268 in the wild and no public exploit code.

Public exploit code:

- Synthetic demo target for EXPOSURE — CVE-2018-21268 (traceroute) + CVE-2018-3757 (pdf-image) (github_poc): https://github.com/dannyEndorTest/node-vulnerable

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-21268 and fix it if it is affected.

What it is: CVE-2018-21268 is a critical command injection vulnerability in n/a, published on 25 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-21268 in the wild and no public exploit code.

Affected packages and fixed versions:
- traceroute (npm): affected all versions up to 1.0.0; no fix listed
- traceroute (npm): affected all versions up to 1.0.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-21268/ (Markdown: https://insights.sbomify.com/CVE-2018-21268/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-21268
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-21268
- OSV: https://osv.dev/vulnerability/CVE-2018-21268

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-21268/
Summaries are generated and may contain mistakes; the official description above is the record.