dbcve.org
OperadriverApplication · Cnpmjs

CVE-2016-10565

HIGH · 8.1 CVSS v3.0 Published 2018-05-31
Fix available
A fix is available. Upgrade to 0.2.3 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
operadriver is a Opera Driver for Selenium. operadriver versions below 0.2.3 download 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 confidence

operadriver versions before 0.2.3 download Opera browser binaries over insecure HTTP connections, allowing a man-in-the-middle attacker to intercept and replace the binary with a malicious one, potentially leading to remote code execution on the victim's machine.

MitigationUpgrade operadriver to version 0.2.3 or later, which uses HTTPS for downloading binary resources. Verify that the updated version correctly establishes secure connections when fetching binaries.

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
OperadriverApplication
Affected:< 0.2.3

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed operadriver version
    Run 'npm list operadriver' in your project directory, or inspect your package.json dependencies section for the operadriver version number
    Affected if The version listed is lower than 0.2.3 (e.g., 0.2.2, 0.2.1, etc.)
  2. Locate operadriver in node_modules
    Navigate to node_modules/operadriver/package.json and read the 'version' field directly
    Affected if The version field shows a version less than 0.2.3
  3. Check for multiple operadriver installations
    Run 'npm ls operadriver' to see if any nested dependencies (indirect dependencies) are pulling in a different version than your direct dependency
    Affected if Any operadriver version shown in the tree is below 0.2.3, even as an indirect dependency

You are affected if any operadriver version in your dependency tree is below 0.2.3, as this version uses insecure HTTP for downloading Opera browser binaries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 0.2.3 or later
Fixed in 0.2.3
Interim mitigation

Upgrade operadriver to version 0.2.3 or later, which uses HTTPS for downloading binary resources. Verify that the updated version correctly establishes secure connections when fetching binaries.

Fix this in Operadriver Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-10565 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-10565 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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