# CVE-2019-17334: TIBCO Spotfire Analyst and Desktop Remote Code Execution Via Shared Files

> An attacker with write access to a shared network file system can execute arbitrary code on other users' machines via malicious DXP files in TIBCO Spotfire.

- **Severity:** High 7.6 (`CVSS:3.0/AV:A/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Dec 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-p7qv-f46f-46p7

## What is CVE-2019-17334?

CVE-2019-17334 is a high-severity code injection vulnerability in TIBCO Spotfire Analyst, published on 17 Dec 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The Visualizations component of TIBCO Software Inc.'s TIBCO Spotfire Analyst, TIBCO Spotfire Analytics Platform for AWS Marketplace, TIBCO Spotfire Deployment Kit, TIBCO Spotfire Desktop, and TIBCO Spotfire Desktop Language Packs contains a vulnerability that theoretically allows an attacker with permission to write DXP files to the Spotfire library to remotely execute code of their choice on the user account of other users who access the affected system. This attack is a risk only when the attacker has write access to a network file system shared with the affected system. Affected releases are TIBCO Software Inc.'s TIBCO Spotfire Analyst: versions 7.11.1 and below, versions 7.12.0, 7.13.0, 7.14.0, 10.0.0, 10.1.0, 10.2.0, 10.3.0, 10.3.1, and 10.3.2, versions 10.4.0, 10.5.0, and 10.6.0, TIBCO Spotfire Analytics Platform for AWS Marketplace: version 10.6.0, TIBCO Spotfire Deployment Kit: versions 7.11.1 and below, TIBCO Spotfire Desktop: versions 7.11.1 and below, versions 7.12.0, 7.13.0, 7.14.0, 10.0.0, 10.1.0, 10.2.0, 10.3.0, 10.3.1, and 10.3.2, versions 10.4.0, 10.5.0, and 10.6.0, and TIBCO Spotfire Desktop Language Packs: versions 7.11.1 and below.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2019-17334?

It affects 5 products.


Products: Tibco Spotfire Analyst, Tibco Spotfire Analytics Platform for Aws, Tibco Spotfire Deployment Kit, Tibco Spotfire Desktop, Tibco Spotfire Desktop Language Packs.

## How do I fix CVE-2019-17334?

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

## Is CVE-2019-17334 being exploited?

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

## Other vulnerabilities in TIBCO Spotfire Analyst

- [CVE-2017-3181](https://insights.sbomify.com/CVE-2017-3181/): SQL injection in Spotfire Analyst (critical 9.8)
- [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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-17334 and fix it if it is affected.

What it is: CVE-2019-17334 is a high-severity code injection vulnerability in TIBCO Spotfire Analyst, published on 17 Dec 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-17334 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-2019-17334/ (Markdown: https://insights.sbomify.com/CVE-2019-17334/index.md)
```

## Sources

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

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