# CVE-2017-3180: Multiple TIBCO Spotfire components fail to sanitize user-supplied inout and are vulnerable to cross-site scripting > Attackers can execute arbitrary scripts in user browsers via unsanitized input, potentially stealing credentials in TIBCO Spotfire products. - **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** No - **Published:** 24 Jul 2018 - **Updated:** 5 Aug 2024 - **Also known as:** GHSA-fw63-53rx-w22v ## What is CVE-2017-3180? CVE-2017-3180 is a medium-severity cross-site scripting vulnerability in TIBCO Silver Fabric Enabler for Spotfire Web Player, published on 24 Jul 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. ### Official description Multiple 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 Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-20 (Improper Input Validation) ## Which versions are affected by CVE-2017-3180? It affects 10 products. Products: Tibco Silver Fabric Enabler for Spotfire Web Player, Tibco Spotfire Analyst, Tibco Spotfire Analytics Platform for Aws, Tibco Spotfire Automation Services, Tibco Spotfire Connectors, Tibco Spotfire Deployment Kit, Tibco Spotfire Desktop, Tibco Spotfire Desktop Language Packs, Tibco Spotfire Professional, Tibco Spotfire Web Player. ## How do I fix CVE-2017-3180? No fix has been published for CVE-2017-3180 yet. Limit exposure of the affected software until one is available. ## Is CVE-2017-3180 being exploited? There is no known exploitation of CVE-2017-3180 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2017-3180 and fix it if it is affected. What it is: CVE-2017-3180 is a medium-severity cross-site scripting vulnerability in TIBCO Silver Fabric Enabler for Spotfire Web Player, published on 24 Jul 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2017-3180 in the wild and no public exploit code. Affected product: TIBCO Silver Fabric Enabler for Spotfire Web Player. 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-2017-3180/ (Markdown: https://insights.sbomify.com/CVE-2017-3180/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2017-3180 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-3180 - OSV: https://osv.dev/vulnerability/CVE-2017-3180 --- From sbomify Insights: https://insights.sbomify.com/CVE-2017-3180/ Summaries are generated and may contain mistakes; the official description above is the record.