Security readout for executives and security teams
Plain-English summary
This issue affects the npm cmake node module, which installs CMake Linux x86 binaries. The module downloads binary resources over HTTP, so someone positioned on the network path could replace the downloaded binary. That could lead to remote code execution during installation or build activity.
Executive priority
Prioritize review if this dependency is used in CI or developer build systems. The business risk is supply-chain execution during software builds, not a remotely reachable production service by default.
Technical view
CVE-2016-10642 is a CWE-311 cleartext transport issue in the cmake node module. Sources state all versions are affected. The risk is binary substitution during HTTP download by an attacker with network-path control, potentially resulting in execution of an attacker-controlled binary.
Likely exposure
Exposure is most likely in projects, CI systems, or developer machines that install the affected cmake node module, especially where installs occur across untrusted or interceptable networks.
Exploitation context
The provided sources do not show active exploitation or CISA KEV listing. Exploitation requires a network-positioned attacker or equivalent ability to interfere with the HTTP binary download.
Researcher notes
Evidence is limited to the CVE description and Node Security advisory reference. No CVSS, patched version, exploit evidence, or detailed remediation is provided in the source bundle.
Mitigation direction
- Check vendor advisory and package guidance before continued use.
- Remove the affected cmake node module where it is not required.
- Replace it with a trusted CMake installation path where feasible.
- Avoid installing affected dependencies over untrusted networks.
- Review build environments for historical binary downloads.
Validation and detection
- Search dependency manifests and lockfiles for the cmake node module.
- Check CI and build scripts for npm installs of cmake.
- Confirm whether current installs still fetch binaries over HTTP.
- Review affected build hosts for unexpected CMake binaries.
- Document whether any production build pipeline uses this dependency.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupExecution 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 lookupCVE-2016-10642 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://nodesecurity.io/advisories/233CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.