dbcve.org
Spotfire AnalystApplication · Tibco

CVE-2017-3181

CRITICAL · 9.8 CVSS v3.0 Published 2018-07-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/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
Multiple TIBCO Products are prone to multiple unspecified SQL-injection vulnerabilities because it fails to properly sanitize user-supplied input before using it in an SQL query. Exploiting these issues could allow an attacker to compromise the application, access or modify data, or exploit latent vulnerabilities in the underlying database. The following products and versions are affected: TIBCO Spotfire Analyst 7.7.0 TIBCO Spotfire Connectors 7.6.0 TIBCO Spotfire Deployment Kit 7.7.0 TIBCO Spotfire Desktop 7.6.0 TIBCO Spotfire Desktop 7.7.0 TIBCO Spotfire Desktop Developer Edition 7.7.0 TIBCO Spotfire Desktop Language Packs 7.6.0 TIBCO Spotfire Desktop Language Packs 7.7.0 The following components are affected: TIBCO Spotfire Client TIBCO Spotfire Web Player Client

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 · moderate confidence

Multiple TIBCO Spotfire products (versions 7.6.0 and 7.7.0) contain SQL injection vulnerabilities in the Client and Web Player Client components due to improper sanitization of user-supplied input before using it in SQL queries. This critical vulnerability (CVSS 9.8) can be exploited remotely without authentication, potentially allowing attackers to execute arbitrary SQL commands, compromise the application, and access or modify sensitive data in the underlying database.

MitigationApply vendor-supplied patches immediately; if no patch is available, implement strict input validation and parameterized queries/prepared statements for all database interactions, and consider restricting network access to affected components until remediation is complete.

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
Spotfire AnalystApplication
Affected:= 7.7.0
Spotfire ClientApplication
Affected:all versions
Spotfire ConnectorsApplication
Affected:= 7.6.0
Spotfire Deployment KitApplication
Affected:= 7.7.0
Spotfire DesktopApplication
Affected:= 7.6.0= 7.7.0
Spotfire Desktop Language PacksApplication
Affected:= 7.6.0= 7.7.0
Spotfire Web Player ClientApplication
Affected:all versions

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/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 installed TIBCO Spotfire product
    Check installed programs or running services for TIBCO Spotfire components such as Spotfire Analyst, Spotfire Client, Spotfire Connectors, Spotfire Desktop, Spotfire Deployment Kit, or Spotfire Web Player Client. Look in Add/Remove Programs on Windows or check installed packages on Linux systems.
    Affected if Any Spotfire product from the affected list is installed
  2. Check Spotfire Client version
    Open the Spotfire Client application and navigate to Help > About, or check the installation directory for version information files. The Client component is vulnerable in all versions.
    Affected if Tibco Spotfire Client is installed (all versions are affected)
  3. Check Spotfire Web Player Client version
    Access the Web Player web interface or check the installation directory for version information. The Web Player Client component is vulnerable in all versions.
    Affected if Tibco Spotfire Web Player Client is installed (all versions are affected)
  4. Verify Spotfire Analyst, Desktop, or Connectors version
    Check the installed version of Tibco Spotfire Analyst (7.7.0), Desktop (7.6.0 or 7.7.0), Connectors (7.6.0), or Deployment Kit (7.7.0) against the affected version ranges.
    Affected if Version matches exactly 7.6.0 or 7.7.0 for the respective products listed
  5. Confirm network exposure
    Determine if the Web Player Client is accessible from the network without authentication. Check firewall rules and web server configuration for the Spotfire Web Player service.
    Affected if Web Player Client is exposed to untrusted networks without authentication

The environment is affected if any TIBCO Spotfire Client or Web Player Client component is installed (all versions), or if Spotfire Analyst/Desktop/Connectors/Deployment Kit matches versions 7.6.0 or 7.7.0, especially if exposed to network access.

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

Apply vendor-supplied patches immediately; if no patch is available, implement strict input validation and parameterized queries/prepared statements for all database interactions, and consider restricting network access to affected components until remediation is complete.

Fix this in Spotfire Analyst Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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