LiveActive security incident?Get immediate response
CVE Record

CVE-2016-10651: webdriver-launcher is a Node.js Selenium Webdriver Launcher.

webdriver-launcher is a Node.js Selenium Webdriver Launcher. webdriver-launcher 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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

webdriver-launcher can download Selenium-related binary resources over unencrypted HTTP. A person who can intercept that network traffic could replace the expected binary with their own, potentially running code on a developer workstation or CI system.

Executive priority

Prioritize if this package runs in CI or developer environments with source-code or deployment access. The main business risk is supply-chain compromise through a replaced binary, but exploitation depends on network-path control.

Technical view

CVE-2016-10651 affects all versions of the webdriver-launcher Node module. The package retrieves binary resources over HTTP, creating a CWE-311 cleartext transport weakness. Sources describe possible RCE if an attacker is positioned on the network path and swaps the requested binary.

Likely exposure

Exposure is most likely in JavaScript projects, test automation, or CI environments that install or run the webdriver-launcher Node module. The source bundle lists all versions as affected, but does not provide CPEs, CVSS, or confirmed fixed versions.

Exploitation context

The cited description requires a man-in-the-middle position or similar ability to alter traffic between the user and remote server. The source bundle does not indicate known active exploitation, and KEV status is false.

Researcher notes

The record has limited technical detail: no CVSS, no exploit confirmation, and no patch version in the provided sources. Treat impact as potentially severe because binary replacement can lead to code execution, but validate actual use before escalating broadly.

Mitigation direction

  • Inventory dependencies and lockfiles for webdriver-launcher usage.
  • Remove or replace webdriver-launcher where feasible, especially in CI.
  • Check vendor or package-maintainer guidance for any supported fix.
  • Avoid running affected tooling on untrusted networks.
  • Restrict CI agents and developer systems from cleartext binary downloads.

Validation and detection

  • Search package manifests and lockfiles for webdriver-launcher.
  • Confirm whether build or test jobs execute the package.
  • Review CI logs for HTTP binary download behavior tied to this package.
  • Verify whether any maintained replacement uses authenticated HTTPS downloads.
  • Document any remaining dependency use and compensating controls.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-311: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2016-10651 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
HackerOnewebdriver-launcher node moduleAll versionsListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-311 · source CWE mapping

Missing Encryption of Sensitive Data

Missing Encryption of Sensitive Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.