CVE-2016-10644
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 · uneditedslimerjs-edge is a npm wrapper for installing the bleeding edge version of slimerjs. slimerjs-edge 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 slimerjs-edge npm package downloads binary resources over unencrypted HTTP connections, allowing attackers positioned on the network to intercept the download and inject malicious code. By performing a man-in-the-middle attack, an attacker could replace the legitimate slimerjs binary with a compromised version, potentially achieving remote code execution on affected systems.
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 slimerjs-edge is installedRun 'npm list slimerjs-edge' or 'ls node_modules/slimerjs-edge' in your project directoryAffected if The package appears in node_modules or npm list output
-
Verify package.json dependencyInspect your project's package.json for 'slimerjs-edge' in the dependencies, devDependencies, or optionalDependencies sectionsAffected if The package is listed as a dependency
-
Inspect download mechanism in package sourceExamine the install script or main JavaScript file in node_modules/slimerjs-edge for HTTP URLs used to fetch binaries (look for http:// URLs pointing to download sources)Affected if The package code contains unencrypted http:// URLs for downloading binary resources
-
Check npm shrinkwrap or lockfileReview npm-shrinkwrap.json or package-lock.json for slimerjs-edge entry and its download source configurationAffected if The lockfile shows slimerjs-edge with HTTP-based download URLs
-
Examine postinstall script behaviorRun 'npm install slimerjs-edge --verbose' and observe the network requests made during installation for http:// (not https://) URLsAffected if The installation process attempts to download binaries over unencrypted HTTP
You are affected if slimerjs-edge is installed and its download mechanism uses unencrypted HTTP URLs to fetch binary 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 HTTP download URLs with HTTPS and implement cryptographic verification (e.g., checksums or signatures) to ensure binary integrity before execution.
- Consultation2.0 h
- Implementation4.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10644 — 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-10644 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