Security readout for executives and security teams
Plain-English summary
frames-compiler can download binary resources over plain HTTP. A network-positioned attacker could replace the downloaded binary, potentially causing code execution during installation or use. This is mainly a software supply-chain and build-environment risk, not evidence of broad internet exploitation.
Executive priority
Prioritize review if this package appears in production build pipelines or developer onboarding scripts. The business risk is compromise of build hosts or developer machines, but urgency is lower without evidence of active exploitation.
Technical view
CVE-2016-10649 affects all versions of the frames-compiler Node module. The issue is CWE-311: sensitive transfer without encryption. The source bundle states HTTP binary downloads may be swapped by an attacker between the user and server, creating possible RCE. No CVSS score, patch, or KEV listing is provided.
Likely exposure
Exposure is likely limited to environments that install or execute the affected frames-compiler package, especially developer workstations, CI runners, or build systems using old Node dependencies.
Exploitation context
The cited evidence describes a man-in-the-middle condition: the attacker must be on the network path or otherwise able to alter the HTTP binary download. The source bundle does not show active exploitation or a public weaponized campaign.
Researcher notes
The evidence is sparse: affected scope is all versions, but no CVSS, fixed version, or exploit-in-the-wild claim is provided. Treat remediation as dependency removal or vendor-guided replacement unless additional authoritative package guidance is found.
Mitigation direction
- Check vendor and package guidance for a safe replacement or removal path.
- Remove frames-compiler from active projects if it is not required.
- Avoid installing affected dependencies on untrusted networks.
- Require TLS or trusted artifact mirrors for build-time binary downloads.
- Restrict CI runners from fetching unauthenticated HTTP binaries.
Validation and detection
- Search package manifests and lockfiles for frames-compiler.
- Review SBOMs and dependency inventories for this module.
- Check CI and build logs for frames-compiler installation or execution.
- Confirm whether any build process fetches binaries over HTTP.
- Record that KEV evidence is not present in the supplied sources.
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-10649 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/247CVE 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.