{"answers":{"affected":"2 open source packages ship an affected version, including traceroute. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-21268 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-21268 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2018-21268 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2018-21268 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- traceroute (npm): affected all versions up to 1.0.0; no fix listed\n- traceroute (npm): affected all versions up to 1.0.0; no fix listed\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2018-21268/ (Markdown: https://insights.sbomify.com/CVE-2018-21268/index.md)","id":"CVE-2018-21268","markdown":"https://insights.sbomify.com/CVE-2018-21268/index.md","name":"CVE-2018-21268","record":{"aliases":["GHSA-8j9v-qhp4-wv55"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js traceroute library","requires_auth":"none","summary":"Remote attackers can execute arbitrary OS commands via the host parameter in the node-traceroute library due to unsafe use of Child.exec().","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"traceroute","vendor":"traceroute_project"}],"cvss":{"score":10,"severity":"critical","source":"cna","vector":"CVSS:3.1/AC:L/AV:N/A:L/C:H/I:H/PR:N/S:C/UI:N","version":"3.1"},"cwes":[{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":"2026-05-21","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-05-21T00:20:15Z","kind":"github_poc","ref":"https://github.com/dannyEndorTest/node-vulnerable","stars":0,"title":"Synthetic demo target for EXPOSURE — CVE-2018-21268 (traceroute) + CVE-2018-3757 (pdf-image)"}],"tier":"poc_unverified"},"has_fix":false,"headline":"Node-Traceroute RCE Vulnerability","id":"CVE-2018-21268","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"command_injection","year":"2018"},"n_packages":2,"n_references":8,"next":{"headline":"Path traversal in n/a","id":"CVE-2018-21269"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["1.0.0"],"package":"traceroute","purl":null,"source":"GHSA-8j9v-qhp4-wv55"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["1.0.0"],"package":"traceroute","purl":"pkg:npm/traceroute","source":"GHSA-8j9v-qhp4-wv55"}],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2018-21267"},"products":["n/a"],"published":"2020-06-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary OS commands via the host parameter in the node-traceroute library due to unsafe use of Child.exec().","url":"https://insights.sbomify.com/CVE-2018-21268/"}