CVE-2016-10636
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 · uneditedgrunt-ccompiler is a Closure Compiler Grunt Plugin. grunt-ccompiler 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 confidencegrunt-ccompiler is a Closure Compiler Grunt plugin that downloads binary resources over HTTP instead of HTTPS, making it vulnerable to man-in-the-middle attacks where an attacker could intercept the download and inject a malicious binary, potentially leading to remote code execution on the victim's system.
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 dataall versionsCVSS 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 grunt-ccompiler is installed as a dependencyInspect your project's package.json file and look for 'grunt-ccompiler' in the dependencies or devDependencies sectionAffected if grunt-ccompiler is listed as a dependency in package.json
-
Locate the grunt-ccompiler package source codeNavigate to node_modules/grunt-ccompiler in your project directory and list its source filesAffected if The package exists in node_modules/grunt-ccompiler
-
Search for HTTP download URLs in the source codeUse grep or a text search to find any 'http://' URLs within the grunt-ccompiler source files, particularly in files that handle binary downloads or compiler retrievalAffected if The source code contains http:// URLs for downloading binaries or compiler resources
-
Inspect the Gruntfile configuration for download settingsExamine your project's Gruntfile.js or Gruntfile.coffee for any configuration related to grunt-ccompiler that specifies download URLs or pathsAffected if The Grunt configuration specifies non-HTTPS URLs for compiler or binary downloads
-
Check for any cached or downloaded compiler binariesLook for any locally stored compiler binaries or temporary download files that may have been fetched by the plugin, typically in node_modules or a temporary directoryAffected if Binary files exist that were downloaded from insecure HTTP sources
Your environment is affected if grunt-ccompiler is installed and its code or configuration uses HTTP URLs to download binaries or compiler resources.
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 all HTTP URLs with HTTPS in the plugin's source code and ensure proper SSL/TLS certificate validation is performed during downloads.
- 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-10636 — 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-10636 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