# CVE-2016-10562: Downloads Resources over HTTP in iedriver

> Attackers can execute remote code by intercepting HTTP downloads of the IEDriver binary, allowing them to replace it with malicious software.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 May 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-jfgq-g48x-jq83

## What is CVE-2016-10562?

CVE-2016-10562 is a high-severity vulnerability in HackerOne iedriver node module, published on 31 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

iedriver is an NPM wrapper for Selenium IEDriver. iedriver versions below 3.0.0 download binary resources over HTTP, which leaves the module 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.

Weakness: CWE-310, CWE-311 (Missing Encryption of Sensitive Data)

## Which versions are affected by CVE-2016-10562?

2 open source packages ship an affected version, including iedriver. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `iedriver` | npm | All versions | 3.0.0 |
| `iedriver` | npm | All versions | 3.0.0 |

Products: Iedriver Project Iedriver.

## How do I fix CVE-2016-10562?

Upgrade iedriver to 3.0.0 or later.

## Is CVE-2016-10562 being exploited?

There is no known exploitation of CVE-2016-10562 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-10562 and fix it if it is affected.

What it is: CVE-2016-10562 is a high-severity vulnerability in HackerOne iedriver node module, published on 31 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-10562 in the wild and no public exploit code.

Affected packages and fixed versions:
- iedriver (npm): affected all versions; fixed in 3.0.0
- iedriver (npm): affected all versions; fixed in 3.0.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-10562/ (Markdown: https://insights.sbomify.com/CVE-2016-10562/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-10562
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-10562
- OSV: https://osv.dev/vulnerability/CVE-2016-10562

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-10562/
Summaries are generated and may contain mistakes; the official description above is the record.