CVE-2019-17334
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 · uneditedThe 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.
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 confidenceTIBCO Spotfire Visualizations component contains a code injection vulnerability where an attacker with write access to DXP files in the Spotfire library can embed malicious code. When other users open these specially crafted DXP files, the embedded code executes in the context of the victim's user account, leading to remote code execution.
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<= 7.11.1= 7.12.0= 7.13.0= 7.14.0= 10.0.0= 10.1.0= 10.2.0= 10.3.0= 10.3.1= 10.3.2= 10.4.0= 10.5.0= 10.6.0<= 7.11.1<= 7.11.1= 7.12.0= 7.13.0= 7.14.0= 10.0.0= 10.1.0= 10.2.0= 10.3.0= 10.3.1= 10.3.2= 10.4.0= 10.5.0<= 7.11.1CVSS 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
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Spotfire product and versionCheck the installed TIBCO Spotfire product version via the application (Help > About Spotfire) or check the installation directory for version information files. Common locations: C:\Program Files\TIBCO\Spotfire\ or /opt/tibco/spotfire/Affected if The installed version matches <= 7.11.1, = 7.12.0, = 7.13.0, = 7.14.0, = 10.0.0, = 10.1.0, = 10.2.0, = 10.3.0, = 10.3.1, = 10.3.2, = 10.4.0, = 10.5.0, or = 10.6.0 (for AWS platform)
-
Locate Spotfire library directoryIdentify the Spotfire library path used in your environment. This is typically configured in the Spotfire Server configuration and points to a network share or local directory where DXP files are stored. Check Spotfire Server configuration files (e.g., bootstrap.xml, configuration.xml) for the library path.Affected if The library directory is accessible over network file systems or lacks proper access controls
-
Check file permissions on the Spotfire libraryReview who has write access to the Spotfire library directory and its DXP files. Use OS-level permissions checking (e.g., icacls on Windows, ls -la on Linux) or consult Spotfire Server admin console for library permissions.Affected if Multiple users or untrusted accounts have write permissions to DXP files in the library
-
Inspect DXP files for unexpected embedded contentExamine DXP files in the library for suspicious XML elements, scripts, or encoded content that does not correspond to normal Spotfire analysis definitions. DXP files are ZIP archives - inspect contents.xml and other XML files inside the DXP for unusual script tags, external references, or encoded payloads.Affected if Any DXP file contains script tags, external entity references, or code that was not created through the normal Spotfire interface
You are affected if you run any of the listed Spotfire versions AND have DXP files in a library where write access is granted to users who should not have it, enabling malicious DXP files to be placed for other users to open.
Generated from the published advisory. Verify against your own configuration.
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 dataRestrict write access to the Spotfire library and network file systems; apply vendor patches/updates to affected Spotfire versions.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-17334 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-17334 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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