CVE-2016-10607
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedopenframe-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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe openframe-glsviewer package downloads binary resources over HTTP without encryption or integrity verification, allowing a man-in-the-middle attacker to intercept and substitute malicious binaries. When the victim installs or updates the package, the attacker-controlled binary is executed, potentially enabling remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 0.2.7CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify if openframe-glsviewer package is installedRun 'npm list openframe-glsviewer' or check package.json dependencies section, or check node_modules for openframe-glsviewer directoryAffected if The package appears in installed dependencies or node_modules
-
Locate package configuration filesFind the package.json for openframe-glsviewer in node_modules/openframe-glsviewer/ and any related configuration files in the projectAffected if Package.json exists and defines download or install scripts
-
Inspect install/update scripts for binary downloadsRead the package.json scripts section, particularly postinstall, preinstall, or install scripts, and look for any commands that fetch binaries or resourcesAffected if Scripts contain commands that download binaries from external sources
-
Check for HTTP (non-HTTPS) URLs in package configurationSearch all package files for HTTP:// URLs, particularly in download scripts, configuration files, or manifest files within node_modules/openframe-glsviewer/Affected if HTTP URLs are found pointing to binary or resource downloads
-
Verify if integrity checking is implementedLook for Subresource Integrity (SRI) hashes, checksum validation, or signature verification in the package download scripts or configurationAffected if No integrity verification mechanism is defined for downloaded binaries
You are affected if openframe-glsviewer is installed and its package configuration uses HTTP URLs to download binaries without any integrity verification mechanism.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace HTTP URLs with HTTPS and implement integrity verification (e.g., Subresource Integrity hashes, checksum validation) for all downloaded binary resources to prevent tampering.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10607 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-10607 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data