Skip to content
Fencer Intel
high 8.1

CVE-2016-10624 json

selenium-chromedriver Downloads Resources over HTTP

published 2018-06-01 8 y ago modified 2026-06-17 4 mo ago also GHSA-7p6h-3fmw-539q , EUVD-2019-0252

cvss
8.1
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.1%
EPSS 2.1% chance of exploitation in 30 days, percentile 81%
public exploits
0
none known

Summary

selenium-chromedriver is a simple utility for downloading the Selenium Webdriver for Google Chrome 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 binary with an attacker controlled binary if the attacker is on the network or positioned in between the user and the remote server.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2016-10624 updated cvss 7.4

selenium-chrome-driver: Downloads Resources over HTTP

  • Red Hat JBoss Fuse Integration Service 2 selenium-chrome-driver selenium-chrome-driver
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.07% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 8.1 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C
GitHub 3.0 8.1 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
npm selenium-chromedriver
<=0.0.2
no fix listed

Affected products

  • HackerOne selenium-chromedriver node module

Classification

Weakness
  • CWE-311 Missing Encryption of Sensitive Data
  • CWE-310 Cryptographic Issues

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.