CVE-2018-5435
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 TIBCO Spotfire Client and TIBCO Spotfire Web Player Client components 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 contain multiple vulnerabilities that may allow for remote code execution. Affected releases are TIBCO Software Inc.'s TIBCO Spotfire Analyst: versions up to and including 7.8.0; 7.9.0; 7.9.1; 7.10.0; 7.10.1; 7.11.0; 7.12.0, TIBCO Spotfire Analytics Platform for AWS Marketplace: versions up to and including 7.12.0, TIBCO Spotfire Deployment Kit: versions up to and including 7.8.0; 7.9.0;7.9.1;7.10.0;7.10.1;7.11.0; 7.12.0, TIBCO Spotfire Desktop: versions up to and including 7.8.0; 7.9.0; 7.9.1; 7.10.0; 7.10.1; 7.11.0;7.12.0, TIBCO Spotfire Desktop Language Packs: versions up to and including 7.8.0; 7.9.0; 7.9.1; 7.10.0; 7.10.1; 7.11.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 · high confidenceTIBCO Spotfire Client and TIBCO Spotfire Web Player Client contain multiple vulnerabilities allowing remote code execution. The CVSS 9.8 score indicates trivial exploitability, likely through deserialization flaws or similar attacks against the client-side components processing untrusted data.
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.8.0= 7.9.0= 7.9.1= 7.10.0= 7.10.1= 7.11.0= 7.12.0<= 7.12.0<= 7.8.0= 7.9.0= 7.9.1= 7.10.0= 7.10.1= 7.11.0= 7.12.0<= 7.8.0= 7.9.0= 7.9.1= 7.10.0= 7.10.1= 7.11.0= 7.12.0<= 7.8.0= 7.9.0= 7.9.1= 7.10.0= 7.10.1= 7.11.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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 TIBCO Spotfire Desktop or Analyst versionOn Windows, open Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell to list installed TIBCO Spotfire products and their versionsAffected if The displayed version is 7.8.0 or lower, or exactly 7.9.0, 7.9.1, 7.10.0, 7.10.1, 7.11.0, or 7.12.0
-
Identify installed TIBCO Spotfire Web Player versionCheck the Spotfire Server administration pages for the Web Player component version, or inspect the installation directory on the server for version information in the bin or config foldersAffected if The Web Player version matches the affected client versions listed (7.8.0 through 7.12.0)
-
Check for TIBCO Spotfire Analytics Platform for AWSIf running Spotfire on AWS, verify the installed Spotfire Analytics Platform version through the AWS marketplace deployment or by checking the local installationAffected if The version is 7.12.0 or lower
-
Check for TIBCO Spotfire Deployment KitVerify if the Spotfire Deployment Kit is installed by checking Program Files for Tibco folder or through Windows Add/Remove ProgramsAffected if The Deployment Kit version is 7.8.0 or lower, or exactly 7.9.0, 7.9.1, 7.10.0, 7.10.1, 7.11.0, or 7.12.0
-
Verify if Spotfire Web Player is network-exposedCheck network configuration or firewall rules to determine if the Spotfire Web Player service is accessible from untrusted networks or the internetAffected if Web Player is exposed to networks outside the trusted internal environment
A user is affected if any TIBCO Spotfire Desktop, Analyst, Web Player, Analytics Platform for AWS, or Deployment Kit installation on their environment is version 7.8.0 through 7.12.0, particularly if the Web Player component is network-accessible.
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 dataUpgrade to a patched version of TIBCO Spotfire Analyst/Desktop (7.11.1 or later for most branches, or latest 7.14+) and ensure Web Player servers are not exposed to untrusted networks.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-5435 — 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-2018-5435 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