LiveActive security incident?Get immediate response
CVE Record

CVE-2016-10593: ibapi is an Interactive Brokers API addon for NodeJS.

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.

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

Security readout for executives and security teams

Plain-English summary

This issue affects the ibapi NodeJS module used with Interactive Brokers APIs. Older versions downloaded binary resources over plain HTTP, allowing a network-positioned attacker to replace the binary in transit. That could lead to remote code execution on systems installing or using the package.

Executive priority

Treat this as high priority where ibapi appears in trading, finance, or CI environments. The main business risk is compromised build or runtime systems through dependency installation, not broad internet-facing scanning.

Technical view

CVE-2016-10593 is a cleartext binary download flaw in the ibapi Node module, mapped to CWE-311. Before version 2.5.6, binary resources were fetched over HTTP, creating a man-in-the-middle substitution risk that could result in attacker-controlled code execution.

Likely exposure

Exposure is most likely on developer workstations, CI systems, build servers, or deployed NodeJS environments that install or execute vulnerable ibapi package versions before 2.5.6.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. Practical exploitation requires an attacker positioned on the network path between the affected system and the download server during the binary retrieval.

Researcher notes

The advisory data supports MITM-based binary replacement and possible RCE before 2.5.6. Severity scoring is absent, and the affected-version data is somewhat imprecise, so confirm package lineage and fix status against the referenced npm and commit sources.

Mitigation direction

  • Upgrade ibapi to version 2.5.6 where applicable.
  • Check vendor and package guidance for any newer maintained replacement.
  • Rebuild affected environments from trusted dependencies.
  • Avoid untrusted networks for dependency installation and build activity.
  • Audit dependency lockfiles for vulnerable ibapi versions.

Validation and detection

  • Search package manifests and lockfiles for ibapi usage.
  • Confirm installed ibapi version is 2.5.6 or otherwise vendor-approved.
  • Review CI and build images for cached vulnerable package versions.
  • Check build logs for cleartext binary downloads tied to ibapi.
  • Verify no production artifact was built from untrusted dependency sources.
Prepared
Confidence
medium
Sources
6

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-10593 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
5Source 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
HackerOneibapi 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