CVE-2019-17337
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 Spotfire library component of TIBCO Software Inc.'s TIBCO Spotfire Analytics Platform for AWS Marketplace and TIBCO Spotfire Server contains a vulnerability that theoretically allows an attacker to perform a reflected cross-site scripting (XSS) attack. Affected releases are TIBCO Software Inc.'s TIBCO Spotfire Analytics Platform for AWS Marketplace: version 10.6.0 and TIBCO Spotfire Server: versions 7.11.7 and below, versions 7.12.0, 7.13.0, 7.14.0, 10.0.0, 10.0.1, 10.1.0, 10.2.0, 10.2.1, 10.3.0, 10.3.1, 10.3.2, 10.3.3, and 10.3.4, versions 10.4.0, 10.5.0, and 10.6.0.
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 confidenceA reflected cross-site scripting (XSS) vulnerability exists in the Spotfire library component of TIBCO Spotfire Analytics Platform for AWS Marketplace and TIBCO Spotfire Server. In reflected XSS attacks, malicious script payloads embedded in crafted URLs are reflected back to the user by the server without proper sanitization, allowing execution of arbitrary JavaScript in the victim's browser session when they interact with the malicious link.
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= 10.6.0<= 7.11.7= 7.12.0= 7.13.0= 7.14.0= 10.0.0= 10.0.1= 10.1.0= 10.2.0= 10.2.1= 10.3.0= 10.3.1= 10.3.2CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Identify TIBCO Spotfire Server versionAccess the TIBCO Spotfire Server administration console (typically at /spotfire/admin) and navigate to the Server Information or Diagnostics section to view the installed version. Alternatively, check the version file in the Spotfire installation directory or review the server startup logs.Affected if The displayed version matches any of these: <=7.11.7; =7.12.0; =7.13.0; =7.14.0; =10.0.0; =10.0.1; =10.1.0; =10.2.0; =10.2.1; =10.3.0; =10.3.1; =10.3.2; or for AWS Marketplace: =10.6.0
-
Identify TIBCO Spotfire Analytics Platform for AWS versionIf using the AWS Marketplace deployment, check the Spotfire deployment configuration or the AWS CloudFormation stack outputs which typically display the Spotfire version. Access the Spotfire server directly and retrieve version information from the administration interface.Affected if The version is exactly 10.6.0 (the only affected AWS Marketplace version listed)
-
Confirm the Spotfire library component is accessibleVerify that the Spotfire web application is accessible by navigating to the Spotfire server URL (such as https://your-server/spotfire/). Attempt to access the library module specifically (typically at /spotfire/library) to confirm this component is exposed.Affected if The Spotfire library interface loads and is accessible to users without authentication restrictions, making the XSS vector possible
-
Test for reflected XSS in library URLsUsing a browser developer tool or a safe testing methodology, construct a test URL pointing to the Spotfire library endpoint with a benign test payload in the URL parameter (such as ?param=<script>alert('test')</script>). Submit the URL and observe whether the payload is reflected unescaped in the response page HTML.Affected if The submitted test payload appears literally in the page source without HTML encoding, indicating the vulnerability is present
A user is affected if they run any of the listed affected versions of TIBCO Spotfire Server or Spotfire Analytics Platform for AWS and the Spotfire library component is accessible without proper input sanitization on URL parameters.
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 dataApply vendor-provided patches from TIBCO for the affected versions. As an interim measure, implement robust input validation and output encoding on server-side endpoints, and deploy Content Security Policy (CSP) headers to mitigate XSS execution.
- 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-17337 — 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-17337 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