CVE-2016-10639
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 · uneditedredis-srvr is a npm wrapper for redis-server. redis-srvr 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 redis-srvr npm package downloads redis-server binary resources over unencrypted HTTP, making it vulnerable to man-in-the-middle (MITM) attacks. An attacker positioned on the network could intercept the HTTP request and replace the legitimate binary with a malicious one, potentially achieving remote code execution on the victim's machine.
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.
-
Identify if redis-srvr is installedCheck your project's package.json for 'redis-srvr' in dependencies, or run 'npm list redis-srvr' to see if it is present in node_modulesAffected if The package is listed as a dependency in package.json or present in node_modules
-
Locate the package download configurationNavigate to node_modules/redis-srvr and examine the source files (often index.js, installer.js, or similar) that handle downloading the redis-server binaryAffected if The package source code exists in node_modules and contains download logic for redis-server
-
Inspect download URLs for HTTP usageOpen the package's download script and search for 'http://' URLs (not 'https://') used to fetch the redis-server binary. Common patterns include 'http://download.redis.io' or similar HTTP endpointsAffected if The download code uses http:// URLs rather than https:// URLs for fetching the binary
-
Verify network traffic would be unencryptedIf the package is used, run a network trace (using a tool like Wireshark or tcpdump) during package installation or when the binary is downloaded, and confirm the traffic uses plain HTTP on port 80Affected if The download traffic is observed traveling over unencrypted HTTP instead of HTTPS
You are affected if redis-srvr is installed as a dependency and its download mechanism uses unencrypted HTTP URLs to fetch the redis-server binary, which could allow an attacker on the same network to substitute a malicious binary during transit.
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 download URLs with HTTPS equivalents to ensure transport layer encryption and integrity verification. Verify that the remote server supports HTTPS and consider adding checksum validation for downloaded binaries.
- 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-10639 — 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-10639 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