dbcve.org
ForextraderApplication · Forex

CVE-2017-5912

MEDIUM · 5.9 CVSS v3.0 Published 2017-05-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
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
The FOREX.com FOREXTrader for iPhone app 2.9.12 through 2.9.14 for iOS does not verify X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information via a crafted certificate.

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 FOREX.com FOREXTrader iPhone app versions 2.9.12-2.9.14 fails to validate SSL/TLS server certificates, allowing man-in-the-middle attackers to intercept traffic by presenting a forged certificate and impersonate the legitimate server to steal sensitive user credentials or financial data.

MitigationImplement proper X.509 certificate chain validation in the app's networking layer, preferably with certificate pinning to bind the app to trusted server certificates.

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
ForextraderApplication
Affected:= 2.9.12= 2.9.13= 2.9.14

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
None
Availability
None

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

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 the installed version of FOREXTrader app
    On the iPhone, go to Settings > General > iPhone Storage (or Settings > Apps > FOREXTrader). Locate the version number displayed under the app name in the App Store, iTunes, or device settings.
    Affected if The version displayed is 2.9.12, 2.9.13, or 2.9.14.
  2. Verify app version via iTunes or App Store listing
    Open iTunes (Windows/Mac) or the App Store on a computer, search for FOREXTrader, and view the version information in the app listing.
    Affected if The listed version matches 2.9.12, 2.9.13, or 2.9.14.
  3. Confirm the app is the official FOREX.com application
    Verify the app developer is listed as 'Forex Capital Markets, LLC' or 'FOREX.com' and the app name is 'FOREXTrader' - ensure it is not a third-party or modified version.
    Affected if The app is the official FOREX.com FOREXTrader iPhone app version 2.9.12-2.9.14.

A user is affected if they have the FOREXTrader iPhone app installed and its version is exactly 2.9.12, 2.9.13, or 2.9.14, as these versions contain the SSL/TLS certificate validation flaw.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper X.509 certificate chain validation in the app's networking layer, preferably with certificate pinning to bind the app to trusted server certificates.

Fix this in Forextrader Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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