dbcve.org
IbapiApplication · Interactivebrokers

CVE-2016-10593

HIGH · 8.1 CVSS v3.0 Published 2018-05-29
Fix available
A fix is available. Upgrade to after 2.4.2 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
ibapi is an Interactive Brokers API addon for NodeJS. ibapi downloads binary resources over HTTP, which leaves it vulnerable to MITM attacks. Before 2.5.6, 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

The ibapi package for Node.js downloads binary resources over unencrypted HTTP without any integrity verification mechanism. This allows man-in-the-middle attackers positioned on the network to intercept the connection and substitute malicious binaries during the download process, potentially leading to remote code execution on affected systems.

MitigationUpgrade ibapi to version 2.5.6 or later which implements secure download mechanisms (HTTPS with integrity verification) to prevent MITM attacks and binary tampering.

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
IbapiApplication
Affected:<= 2.4.2

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. Identify ibapi package version
    Run 'npm list ibapi' or check package.json dependencies to see the installed version of the ibapi package
    Affected if The installed version is 2.4.2 or lower
  2. Locate ibapi in project dependencies
    Check package.json for 'ibapi' entry under dependencies or devDependencies, or search node_modules for ibapi folder
    Affected if The package is listed in dependencies or present in node_modules
  3. Verify download mechanism configuration
    Inspect any configuration files or scripts that reference ibapi downloads, or examine network requests made by the application for HTTP (not HTTPS) connections to download.ibgroup.com or similar IB download hosts
    Affected if Downloads occur over HTTP without integrity verification

A system is affected if the ibapi package version is 2.4.2 or lower and the application downloads binary resources over unencrypted HTTP connections.

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 a release after 2.4.2
Interim mitigation

Upgrade ibapi to version 2.5.6 or later which implements secure download mechanisms (HTTPS with integrity verification) to prevent MITM attacks and binary tampering.

Fix this in Ibapi Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-10593 — 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-10593 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