LiveActive security incident?Get immediate response
CVE Record

CVE-2016-10663: wixtoolset is a Node module wrapper around the wixtoolset binaries wixtoolset downloads binary resources ov...

wixtoolset is a Node module wrapper around the wixtoolset binaries wixtoolset downloads binary resources over HTTP, which leaves it vulnerable to MITM attacks. It may be possible to cause remote code execution (RCE) by swapping out the requested resources with an attacker controlled copy if the attacker is on the network or positioned in between the user and the remote server.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This CVE affects the wixtoolset Node module, which wraps WiX Toolset binaries. The module downloads binary resources over HTTP, so someone positioned on the network could replace those resources during download. The reported impact is possible remote code execution, but the sources do not provide a CVSS score, fixed version, or evidence of active exploitation.

Executive priority

Treat this as a supply-chain hygiene issue with possible code execution impact. It is most urgent where the module is used in CI, release engineering, or developer environments that install dependencies across untrusted networks. No active exploitation is reported in the supplied sources.

Technical view

CVE-2016-10663 is a CWE-311 issue in the wixtoolset Node module. All versions are listed as affected. The risk comes from downloading binary resources over unencrypted HTTP, allowing a man-in-the-middle attacker to swap the requested binary with attacker-controlled content, potentially leading to code execution during install or use.

Likely exposure

Exposure is most likely in projects or build environments that depend on the wixtoolset Node module and allow it to retrieve binaries over HTTP. The source bundle lists all versions as affected, but does not identify specific package versions, platforms, or downstream products beyond the Node module.

Exploitation context

The cited description requires an attacker to be on the network path or otherwise positioned between the user and the remote server. KEV status is false, and the provided sources do not state that exploitation is active in the wild.

Researcher notes

Evidence is limited to the CVE description, Node Security advisory reference, and GitHub issue reference. The bundle provides no CVSS vector, no fixed version, and no confirmed exploit activity. Validation should focus on dependency presence and whether HTTP binary downloads occur in reachable build or developer workflows.

Mitigation direction

  • Check the Node Security advisory and GitHub issue for current vendor guidance.
  • Inventory projects and build systems for the wixtoolset Node module.
  • Avoid dependency installation on untrusted or interceptable networks.
  • Disable automated HTTP binary retrieval where operationally feasible.
  • Use trusted internal artifacts if your organization already supports verified package mirroring.

Validation and detection

  • Search package manifests and lockfiles for the wixtoolset Node module.
  • Review CI and developer build logs for wixtoolset binary downloads over HTTP.
  • Confirm whether installations occur only on trusted networks.
  • Check whether internal package controls verify or mirror downloaded binaries.
  • Document any affected build pipeline before changing dependency behavior.
Prepared
Confidence
medium
Sources
4

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.

cwe · low confidence lookup

CWE-311: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
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-2016-10663 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
3Source 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
HackerOnewixtoolset node moduleAll versionsListed
Weakness

CWE details

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

CWE-311 · source CWE mapping

Missing Encryption of Sensitive Data

Missing Encryption of Sensitive Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.