Security readout for executives and security teams
Plain-English summary
Kindlegen Node module versions before 1.1.0 fetched binary resources over unencrypted HTTP. A network-positioned attacker could replace the downloaded binary, potentially causing code execution on developer workstations or CI systems that install the package.
Executive priority
Treat as a targeted build-chain risk, not a broad internet-facing emergency. Prioritize remediation where CI systems or developer machines install the affected package, because compromise there can affect software output.
Technical view
CVE-2016-10575 is a CWE-311 issue in the kindlegen Node module before 1.1.0. The package downloaded official kindlegen binary resources over HTTP, allowing a man-in-the-middle to substitute an attacker-controlled binary during retrieval.
Likely exposure
Exposure is likely limited to projects that install or build with the kindlegen Node module version below 1.1.0, especially in CI, developer machines, or build environments using untrusted or interceptable networks.
Exploitation context
The source describes possible RCE only when an attacker is on the network path or otherwise positioned between the user and remote server. The bundle does not cite active exploitation, and KEV is false.
Researcher notes
No CVSS score is provided in the bundle. The key condition is insecure HTTP binary download, not a runtime application endpoint. Evidence supports MITM-dependent binary substitution risk and possible RCE, but not exploitation in the wild.
Mitigation direction
- Upgrade kindlegen Node module to version 1.1.0 or later.
- Remove the package if it is no longer required.
- Review lockfiles for kindlegen versions below 1.1.0.
- Check vendor or package advisory guidance before rebuilding affected environments.
Validation and detection
- Search package manifests and lockfiles for kindlegen dependency versions.
- Inspect CI build logs for installation of kindlegen below 1.1.0.
- Confirm dependency resolution installs version 1.1.0 or later.
- Review developer and build images for cached vulnerable package versions.
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-10575 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/251CVE 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.