LiveActive security incident?Get immediate response
CVE Record

CVE-2018-13797: The macaddress module before 0.2.9 for Node.js is prone to an arbitrary command injection flaw, due to allo...

The macaddress module before 0.2.9 for Node.js is prone to an arbitrary command injection flaw, due to allowing unsanitized input to an exec (rather than execFile) call.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2018-13797 affects the Node.js macaddress package before 0.2.9. The package used unsanitized input in a command execution path, creating a command injection risk. For a business, the concern is any application or service that still ships this old dependency.

Executive priority

Treat this as a high-priority dependency cleanup item for Node.js estates, especially externally exposed services. There is no supplied evidence of active exploitation, but command injection in application dependencies can become serious when reachable.

Technical view

The source description says macaddress before 0.2.9 passed unsanitized input to an exec call instead of using execFile. That pattern can allow arbitrary command injection when attacker-controlled data reaches the command construction path. The provided sources identify 0.2.9, a pull request, and a commit as the relevant upstream fix trail.

Likely exposure

Exposure is likely limited to Node.js applications that directly or transitively include macaddress versions earlier than 0.2.9. Actual reachability depends on whether the vulnerable code path is used and whether untrusted input can influence it.

Exploitation context

The source bundle does not show CISA KEV listing, confirmed active exploitation, public exploit code, or observed campaigns. Public GitHub references and discussion exist, so defenders should treat dependency presence as actionable but not assume active exploitation from these sources alone.

Researcher notes

Key uncertainties remain: no CVSS vector, CWE, exploit status, or detailed affected-product metadata is supplied. The strongest evidence is the CVE description plus upstream PR, commit, and 0.2.9 release references showing the exec-to-execFile remediation path.

Mitigation direction

  • Upgrade macaddress to version 0.2.9 or later.
  • Regenerate lockfiles so transitive dependency resolution cannot retain vulnerable versions.
  • Check vendor or maintainer guidance for any application-specific remediation notes.
  • Prioritize internet-facing Node.js services that include this dependency.
  • Redeploy affected services after dependency updates are verified.

Validation and detection

  • Search package manifests and lockfiles for macaddress versions below 0.2.9.
  • Use dependency scanning to identify direct and transitive use.
  • Confirm production artifacts contain the updated package version.
  • Review application usage to determine whether vulnerable functionality is reachable.
  • Check release notes and commit history against the deployed dependency version.
Prepared
Confidence
medium
Sources
6

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-13797 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

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.