# CVE-2017-3181: SQL injection in Spotfire Analyst

> Attackers can execute arbitrary SQL commands via unsanitized input in TIBCO Spotfire components, potentially accessing or modifying data.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-gxcx-xp38-vxx9

## What is CVE-2017-3181?

CVE-2017-3181 is a critical SQL injection vulnerability in TIBCO Spotfire Analyst, published on 24 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2017-3181?

It affects 7 products.


Products: Tibco Spotfire Analyst, Tibco Spotfire Client, Tibco Spotfire Connectors, Tibco Spotfire Deployment Kit, Tibco Spotfire Desktop, Tibco Spotfire Desktop Language Packs, Tibco Spotfire Web Player Client.

## How do I fix CVE-2017-3181?

No fix has been published for CVE-2017-3181 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-3181 being exploited?

There is no known exploitation of CVE-2017-3181 in the wild and no public exploit code.

## Other vulnerabilities in TIBCO Spotfire Analyst

- [CVE-2018-5435](https://insights.sbomify.com/CVE-2018-5435/): TIBCO Spotfire Product Family Remote Code Execution Vulnerability (critical 9.6)
- [CVE-2025-3115](https://insights.sbomify.com/CVE-2025-3115/): Spotfire Data Function Vulnerability (critical 9.4)
- [CVE-2022-41558](https://insights.sbomify.com/CVE-2022-41558/): TIBCO Spotfire Stored Cross Site Scripting (XSS) Vulnerability (critical 9.0)
- [CVE-2020-9416](https://insights.sbomify.com/CVE-2020-9416/): TIBCO Spotfire Stored Cross Site Scripting Vulnerability (high 8.2)
- [CVE-2019-17334](https://insights.sbomify.com/CVE-2019-17334/): TIBCO Spotfire Analyst and Desktop Remote Code Execution Via Shared Files (high 7.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-3181 and fix it if it is affected.

What it is: CVE-2017-3181 is a critical SQL injection vulnerability in TIBCO Spotfire Analyst, published on 24 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-3181 in the wild and no public exploit code.

Affected product: TIBCO Spotfire Analyst. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-3181/ (Markdown: https://insights.sbomify.com/CVE-2017-3181/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-3181
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-3181
- OSV: https://osv.dev/vulnerability/CVE-2017-3181

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-3181/
Summaries are generated and may contain mistakes; the official description above is the record.