CVE-2017-3180
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 · uneditedMultiple TIBCO Products are prone to multiple unspecified cross-site scripting vulnerabilities because it fails to properly sanitize user-supplied input. An attacker may leverage these issues to execute arbitrary script code in the browser of an unsuspecting user in the context of the affected site. This can allow the attacker to steal cookie-based authentication credentials and to launch other attacks. The products and versions that are affected include the following: TIBCO Silver Fabric Enabler for Spotfire Web Player 2.1.2 and earlier TIBCO Spotfire Analyst 7.5.0 TIBCO Spotfire Analyst 7.6.0 TIBCO Spotfire Analyst 7.7.0 TIBCO Spotfire Analytics Platform for AWS Marketplace 7.0.2 and earlier TIBCO Spotfire Automation Services 6.5.3 and earlier TIBCO Spotfire Automation Services 7.0.0, and 7.0.1 TIBCO Spotfire Connectors 7.6.0 TIBCO Spotfire Deployment Kit 6.5.3 and earlier TIBCO Spotfire Deployment Kit 7.0.0, and 7.0.1 TIBCO Spotfire Deployment Kit 7.5.0 TIBCO Spotfire Deployment Kit 7.6.0 TIBCO Spotfire Deployment Kit 7.7.0 TIBCO Spotfire Desktop 6.5.2 and earlier TIBCO Spotfire Desktop 7.0.0, and 7.0.1 TIBCO Spotfire Desktop 7.5.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.0.1 and earlier TIBCO Spotfire Desktop Language Packs 7.5.0 TIBCO Spotfire Desktop Language Packs 7.6.0 TIBCO Spotfire Desktop Language Packs 7.7.0 TIBCO Spotfire Professional 6.5.3 and earlier TIBCO Spotfire Professional 7.0.0 and 7.0.1 TIBCO Spotfire Web Player 6.5.3 and earlier TIBCO Spotfire Web Player 7.0.0 and 7.0.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 confidenceMultiple TIBCO Spotfire products contain cross-site scripting (XSS) vulnerabilities due to insufficient sanitization of user-supplied input. Attackers can inject arbitrary JavaScript code into web pages viewed by unsuspecting users, enabling session hijacking through cookie theft and other client-side attacks.
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<= 2.1.2= 7.5.0= 7.6.0= 7.7.0<= 7.0.2<= 6.5.3= 7.0.0= 7.0.1= 7.6.0<= 6.5.3= 7.0.0= 7.0.1= 7.5.0= 7.6.0= 7.7.0<= 6.5.2= 7.0.0= 7.0.1= 7.5.0= 7.6.0= 7.7.0<= 7.0.1= 7.5.0= 7.6.0= 7.7.0CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed TIBCO Spotfire productsCheck the Windows Programs and Features list, or inspect the installation directory (commonly C:\Program Files\TIBCO\ or /opt/tibco/) for Spotfire-related subdirectoriesAffected if Any TIBCO Spotfire product is present on the system
-
Determine installed product versionLocate version information in the product's About dialog, version.txt file, or check assembly metadata in the installation folderAffected if The version matches any of the affected versions listed: Silver Fabric Enabler <= 2.1.2, Analyst 7.5.0/7.6.0/7.7.0, Analytics Platform for AWS <= 7.0.2, Automation Services <= 6.5.3 or 7.0.0-7.0.1, Connectors 7.6.0, Deployment Kit <= 6.5.3 or 7.0.0-7.0.1 or 7.5.0-7.7.0, Desktop <= 6.5.2 or 7.0.0-7.0
-
Verify if web components are enabledCheck if Spotfire Web Player, Analyst web services, or other web-facing components are installed and running. Look for IIS/apache configurations or Windows services related to Spotfire web functionalityAffected if Web-facing Spotfire components are enabled and accessible to users
-
Inspect web application configurationReview the Spotfire server configuration files (such as spotfire-config.xml or similar) for input validation settings, and examine the web application's response headers for XSS protection directivesAffected if No input sanitization or XSS protection measures are configured in the web application
If any TIBCO Spotfire product is installed and its version matches the affected ranges AND web components are enabled, the environment is likely vulnerable to CVE-2017-3180 XSS attacks.
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-supplied patches for all affected TIBCO Spotfire product versions. Until patches are available, implement input validation and output encoding, and consider deploying a web application firewall as a temporary compensating control.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-3180 — 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-2017-3180 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