LiveActive security incident?Get immediate response
CVE Record

CVE-2016-10687: windows-selenium-chromedriver is a module that downloads the Selenium Jar file.

windows-selenium-chromedriver is a module that downloads the Selenium Jar file. windows-selenium-chromedriver 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 resources with an attacker controlled copy if the attacker is on the network or positioned in between the user and the remote server.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2016-10687 affects the windows-selenium-chromedriver Node module. It downloads a Selenium Jar over unencrypted HTTP. If an attacker can intercept that network connection, they may replace the file with a malicious copy, creating possible remote code execution risk.

Executive priority

Treat this as a build-chain risk with possible code execution, not as a confirmed internet-exploited emergency. Prioritize environments that install dependencies automatically or handle privileged credentials.

Technical view

The issue is CWE-311: sensitive binary resource retrieval without transport encryption. The source bundle states all versions of windows-selenium-chromedriver are affected. The risk depends on whether the package is installed or executed in build, CI, developer, or runtime environments where HTTP downloads can be intercepted.

Likely exposure

Exposure is most likely in Node.js projects, CI jobs, developer workstations, or build systems that install or use windows-selenium-chromedriver. Production exposure depends on whether the package is present and whether its download path runs there.

Exploitation context

The bundle describes possible RCE through malicious binary replacement by a network-positioned attacker. It does not cite public exploitation, KEV listing, exploit code, or a confirmed fixed version.

Researcher notes

Evidence is limited to the CVE record and Node Security advisory reference. No CVSS score, patch version, or active exploitation evidence is provided. The key validation question is whether the vulnerable HTTP download occurs in current workflows.

Mitigation direction

  • Check vendor or package advisory guidance before deciding remediation.
  • Remove or replace windows-selenium-chromedriver where it is not required.
  • Avoid relying on HTTP binary downloads in build pipelines.
  • Use trusted networks and verified artifacts for dependency installation.
  • Prioritize remediation in CI and developer environments handling sensitive code.

Validation and detection

  • Search package manifests and lockfiles for windows-selenium-chromedriver.
  • Check CI images and build scripts for package installation or execution.
  • Identify whether the Selenium Jar download path is still reachable.
  • Review dependency scan results for CVE-2016-10687.
  • Confirm affected systems are not using untrusted network paths during installs.
Prepared
Confidence
medium
Sources
3

Public sources used

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-10687 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
HackerOnewindows-selenium-chromedriver node moduleAll versionsListed
Weakness

CWE details

CWE-311

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.

Open CWE intelligenceSame-CWE CVEs