LiveActive security incident?Get immediate response
CVE Record

CVE-2018-21268: The traceroute (aka node-traceroute) package through 1.0.0 for Node.js allows remote command injection via...

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.

CriticalCVSS 10Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A vulnerable Node.js traceroute package can let a remote user turn a hostname input into operating-system command execution. For an exposed diagnostic feature, this could mean full compromise of the application environment, not just a bad traceroute result.

Executive priority

Prioritize same-day triage where Node.js applications expose host lookup or traceroute features to users. It is not KEV-listed in the provided data, but potential remote command execution makes confirmed exposure a critical remediation item.

Technical view

CVE-2018-21268 affects the traceroute, also called node-traceroute, npm package through 1.0.0. The package used Child.exec() with the host parameter, allowing command injection through crafted input. CVSS 3.1 is 10.0 with network attack vector, no privileges, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is likely limited to Node.js applications that include traceroute through 1.0.0 and pass externally controlled host values into it. Highest-risk cases are internet-facing diagnostics, support tooling, admin panels, APIs, or automation jobs that accept hostnames or IPs from users.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. Public references describe the vulnerability class and affected npm package. Exploitability depends on whether application code exposes the vulnerable host parameter to untrusted input.

Researcher notes

Do not assume broad enterprise exposure from the CVE alone. The key research question is application reachability: whether attacker-controlled host input reaches the vulnerable Child.exec() call in traceroute through 1.0.0. The bundle does not provide a specific fixed version.

Mitigation direction

  • Inventory Node.js projects for traceroute or node-traceroute through version 1.0.0.
  • Remove the package where traceroute functionality is not business-critical.
  • Update or replace the package according to npm, Snyk, or maintainer guidance.
  • Block untrusted input from reaching traceroute host parameters.
  • Disable exposed network diagnostic endpoints until remediation is verified.

Validation and detection

  • Check package.json and lockfiles for traceroute or node-traceroute dependencies.
  • Trace application routes or jobs that pass user-controlled host values into the package.
  • Confirm deployed artifacts do not include vulnerable versions through 1.0.0.
  • Review logs for suspicious use of traceroute-related endpoints or diagnostics.
  • Verify dependency scanners flag and clear CVE-2018-21268 after remediation.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-21268 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
10 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AC:L/AV:N/A:L/C:H/I:H/PR:N/S:C/UI:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
9Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
10CVSS 3.1CriticalCVSS:3.1/AC:L/AV:N/A:L/C:H/I:H/PR:N/S:C/UI:N3.96Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

10Critical
CVSS 3.1 vector shape for CVE-2018-21268Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AC:L/AV:N/A:L/C:H/I:H/PR:N/S:C/UI:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.