CVE-2016-10601
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 · uneditedwebdrvr is a npm wrapper for Selenium Webdriver including Chromedriver / IEDriver / IOSDriver / Ghostdriver. webdrvr 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 webdrvr npm package downloads Selenium WebDriver binaries (Chromedriver, IEDriver, IOSDriver, Ghostdriver) over unencrypted HTTP instead of HTTPS, allowing a network-based attacker to perform MITM attacks and substitute malicious binaries during download, 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 data<= 2.43.0-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 webdrvr package is installedRun 'npm list webdrvr' or inspect package.json for 'webdrvr' in dependenciesAffected if webdrvr appears in installed packages or package.json dependencies
-
Verify the installed versionRun 'npm list webdrvr' to see the installed version number, or check node_modules/webdrvr/package.json for the version fieldAffected if version is 2.43.0-1 or lower (any version <= 2.43.0-1)
-
Locate the webdrvr configurationInspect the webdrvr installation directory, typically node_modules/webdrvr/, for configuration files such as downloader.js, config.js, or similar files that define download URLsAffected if configuration files exist and define download behavior for WebDriver binaries
-
Check for HTTP (non-HTTPS) download URLsSearch within the webdrvr package files for 'http://' strings, particularly in configuration or download scripts. Run: grep -r 'http://' node_modules/webdrvr/Affected if any URL beginning with 'http://' is found (without SSL/TLS) pointing to Selenium WebDriver binary sources like chromedriver, iedriver, or ghostdriver
A user is affected if webdrvr version 2.43.0-1 or lower is installed and the package or its configuration contains HTTP URLs for downloading Selenium WebDriver 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 all HTTP download URLs with HTTPS and implement proper SSL/TLS certificate validation to ensure binaries are downloaded securely and originate from trusted sources.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10601 — 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-10601 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