LiveActive security incident?Get immediate response
CVE Record

CVE-2016-10607: openframe-glsviewer is a Openframe extension which adds support for shaders via glslViewer.

openframe-glsviewer is a Openframe extension which adds support for shaders via glslViewer. openframe-glsviewer 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 binary with an attacker controlled binary 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 vulnerability affects the openframe-glslviewer/openframe-glsviewer Node module, an Openframe extension for shader support. It retrieves binary resources over HTTP, so someone positioned on the network could substitute a malicious binary. Sources describe possible remote code execution, but provide no CVSS score, patch details, or evidence of active exploitation.

Executive priority

Treat as a targeted supply-chain exposure, not a broad internet-facing emergency. Prioritize environments that use Openframe devices or run this module on networks where traffic could be intercepted.

Technical view

CVE-2016-10607 is a CWE-311 issue: binary resource downloads use unencrypted HTTP. A network man-in-the-middle could replace the requested binary with attacker-controlled content, potentially leading to RCE. The bundle lists all versions of the openframe-glslviewer node module as affected and does not name a fixed version.

Likely exposure

Exposure is most likely in systems, images, or projects that include the Openframe openframe-glslviewer/openframe-glsviewer Node module, especially where binary resources are retrieved across untrusted or shared networks.

Exploitation context

The source bundle does not show KEV listing or cited active exploitation. Exploitation appears conditional on attacker network positioning or control of traffic between the user and remote server.

Researcher notes

The public data is sparse and naming is inconsistent between openframe-glsviewer and openframe-glslviewer. No CVSS vector, fixed version, or exploitation evidence is provided in the bundle, so assessment should focus on dependency presence and network trust assumptions.

Mitigation direction

  • Check vendor and advisory guidance for any fixed release or supported replacement.
  • Remove the affected module where shader support is not required.
  • Avoid using the module on untrusted or shared networks.
  • Review dependency and build policies for HTTP binary downloads.
  • Pin approved artifacts through trusted internal distribution where feasible.

Validation and detection

  • Inventory Node.js projects for openframe-glslviewer and openframe-glsviewer references.
  • Confirm whether any production, kiosk, or CI systems use the module.
  • Review package behavior for HTTP binary resource retrieval.
  • Check proxy or network logs for related HTTP binary downloads.
  • Document whether exposure is runtime, build-time, or unused dependency only.
Prepared
Confidence
medium
Sources
3

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-10607 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
2Source 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
HackerOneopenframe-glslviewer 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.