CVE-2016-10677
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 · uneditedgoogle-closure-tools-latest is a Node.js module wrapper for downloading the latest version of the Google Closure tools google-closure-tools-latest 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 resources with an attacker controlled copy 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 google-closure-tools-latest npm package downloads Google Closure binary tools over unencrypted HTTP instead of HTTPS, enabling Man-in-the-Middle attackers to intercept and replace the downloaded resources with malicious code. This supply chain vulnerability allows remote code execution on any system running this package if an attacker is positioned on the network path.
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.1.1CVSS 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.
-
Check if google-closure-tools-latest is a project dependencyExamine your project's package.json file for 'google-closure-tools-latest' in the dependencies or devDependencies section. Also run 'npm list google-closure-tools-latest' to see if it is installed.Affected if The package is listed as a dependency in package.json or appears in npm list output.
-
Determine the installed versionRun 'npm list google-closure-tools-latest --depth=0' or inspect node_modules/google-closure-tools-latest/package.json to find the installed version number.Affected if The installed version is 0.1.1 or lower.
-
Inspect the package download mechanismExamine the main entry file in node_modules/google-closure-tools-latest (often index.js or a bin script) and look for HTTP URLs used to fetch Google Closure binaries.Affected if The code contains 'http://' URLs pointing to download locations for Closure tools instead of 'https://'.
-
Check npm audit outputRun 'npm audit' or 'npm audit --json' in the project directory to see if this CVE is reported in the security audit results.Affected if The audit output lists CVE-2016-10677 or references the insecure HTTP download vulnerability for this package.
You are affected if google-closure-tools-latest version 0.1.1 or lower is installed and the package code uses unencrypted HTTP URLs to fetch remote binaries.
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 cryptographic verification (e.g., checksums or signatures) for downloaded binaries to ensure integrity. Consider migrating to a package manager installation method or alternative maintained tools.
- Consultation4.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10677 — 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-10677 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