dbcve.org
Spotfire AnalystApplication · Tibco

CVE-2020-9416

MEDIUM · 5.4 CVSS v3.1 Published 2020-09-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 Spotfire client component of TIBCO Software Inc.'s TIBCO Spotfire Analyst, TIBCO Spotfire Analytics Platform for AWS Marketplace, TIBCO Spotfire Desktop, and TIBCO Spotfire Server contains a vulnerability that theoretically allows a legitimate user to inject scripts. If executed by a victim authenticated to the affected system these scripts will be executed at the privileges of the victim. Affected releases are TIBCO Software Inc.'s TIBCO Spotfire Analyst: versions 10.7.0, 10.8.0, 10.9.0, and 10.10.0, TIBCO Spotfire Analytics Platform for AWS Marketplace: versions 10.7.0, 10.8.0, 10.8.1, 10.9.0, 10.10.0, and 10.10.1, TIBCO Spotfire Desktop: versions 10.7.0, 10.8.0, 10.9.0, and 10.10.0, and TIBCO Spotfire Server: versions 10.7.0, 10.8.0, 10.8.1, 10.9.0, 10.10.0, and 10.10.1.

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

This is a script injection vulnerability in TIBCO Spotfire client components where a legitimate authenticated user can inject malicious scripts that execute in the context of other authenticated users' sessions at their privilege level. The vulnerability exists in the client-side processing of user-supplied content that is not properly sanitized before rendering.

MitigationApply the vendor-provided patch from TIBCO for the affected Spotfire versions. Until patched, limit user permissions and monitor for suspicious script injection attempts in user-generated content.

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:= 10.7.0= 10.8.0= 10.9.0= 10.10.0
Spotfire Analytics PlatformApplication
Affected:= 10.7.0= 10.8.0= 10.8.1= 10.9.0= 10.10.0= 10.10.1
Spotfire DesktopApplication
Affected:= 10.7.0= 10.8.0= 10.9.0= 10.10.0
Spotfire ServerApplication
Affected:= 10.7.0= 10.8.0= 10.8.1= 10.9.0= 10.10.0= 10.10.1

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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. Identify installed Spotfire product and version
    Check the installed TIBCO Spotfire version. For Desktop/Analyst: open the application, go to Help > About. For Server: log into the Spotfire Server admin console or check the installation directory version file. For Analytics Platform: check the installed package version.
    Affected if The installed version matches 10.7.0, 10.8.0, 10.8.1, 10.9.0, 10.10.0, or 10.10.1 for any of the affected products (Spotfire Analyst, Desktop, Analytics Platform, or Server).
  2. Confirm user-generated content feature is active
    Determine if the Spotfire deployment allows users to create or upload content such as data visualizations, analysis files, text annotations, or embedded scripts. This is default behavior in Spotfire where authenticated users create and share analysis content.
    Affected if The system allows authenticated users to create, upload, or share content that gets rendered to other users, which is the standard operational mode.
  3. Review content rendering paths
    Examine how user-supplied content is processed and displayed in the Spotfire client. Check if content authored by one user is rendered in sessions of other users, particularly through features like analysis files, data tables, text areas, or visualization overlays.
    Affected if User-created content is rendered in the sessions of other authenticated users without server-side sanitization, which is the default behavior in unpatched versions.

You are affected if your installed Spotfire version matches any of the listed versions (10.7.0 through 10.10.1) and users can create or share content that gets rendered to other users, which is the standard operational mode.

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 the vendor-provided patch from TIBCO for the affected Spotfire versions. Until patched, limit user permissions and monitor for suspicious script injection attempts in user-generated content.

Fix this in Spotfire Analyst Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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