dbcve.org
Spotfire Analytics Platform For AwsApplication · Tibco

CVE-2018-18814

CRITICAL · 9.8 CVSS v3.0 Published 2019-01-16
Fix available
A fix is available. Upgrade to after 10.0.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 TIBCO Spotfire authentication component of TIBCO Software Inc.'s TIBCO Spotfire Analytics Platform for AWS Marketplace, and TIBCO Spotfire Server contains a vulnerability in the handling of the authentication that theoretically may allow an attacker to gain full access to a target account, independent of configured authentication mechanisms. Affected releases are TIBCO Software Inc. TIBCO Spotfire Analytics Platform for AWS Marketplace: versions up to and including 10.0.0, and TIBCO Spotfire Server: versions up to and including 7.10.1; 7.11.0; 7.11.1; 7.12.0; 7.13.0; 7.14.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 confidence

TIBCO Spotfire Server and Analytics Platform for AWS Marketplace contain an authentication bypass vulnerability in their authentication component. The flaw theoretically allows an attacker to gain full access to target accounts regardless of configured authentication mechanisms, achieving critical severity due to the complete account takeover possibility.

MitigationApply vendor-provided patches or upgrade to TIBCO Spotfire versions beyond the affected releases (10.0.0 for AWS Marketplace and beyond 7.14.0 for Spotfire Server). Verify all authentication mechanisms function correctly after patching.

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 Analytics Platform For AwsApplication
Affected:<= 10.0.0
Spotfire ServerApplication
Affected:<= 7.10.1= 7.11.0= 7.11.1= 7.12.0= 7.13.0= 7.14.0

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify TIBCO Spotfire Server version
    Access the Spotfire Server administration interface and navigate to About/Server Information, or inspect the version file in the Spotfire installation directory (commonly found in the config or bin directory as version.txt or similar).
    Affected if The installed version is 7.10.1 or lower, OR any of these specific versions: 7.11.0, 7.11.1, 7.12.0, 7.13.0, 7.14.0, OR for AWS Marketplace version 10.0.0 or lower.
  2. Confirm Spotfire Server deployment type
    Determine whether the deployment is the Spotfire Server product or the Spotfire Analytics Platform for AWS Marketplace. Check the product name in the installation or AWS Marketplace console.
    Affected if The deployment is either Spotfire Server (any version listed in affected ranges) or Spotfire Analytics Platform for AWS Marketplace version 10.0.0 or lower.
  3. Verify authentication component is in use
    Review the Spotfire Server configuration to confirm that authentication mechanisms are configured and enabled. Check configuration files such as bootstrap.xml or authentication configuration in the Spotfire admin tool.
    Affected if Authentication is configured and the server is actively using authentication to protect access.
  4. Check server accessibility
    Determine if the Spotfire Server web interface or API endpoints are exposed to network access. Review firewall rules, load balancer settings, or network ACLs controlling access to the server.
    Affected if The server is accessible from network segments beyond the trusted internal network.

You are affected if your TIBCO Spotfire deployment matches one of the version ranges (7.10.1 or lower, 7.11.0-7.14.0, or AWS Marketplace 10.0.0 or lower) and authentication is actively configured and the server is network-accessible.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 10.0.0
Interim mitigation

Apply vendor-provided patches or upgrade to TIBCO Spotfire versions beyond the affected releases (10.0.0 for AWS Marketplace and beyond 7.14.0 for Spotfire Server). Verify all authentication mechanisms function correctly after patching.

Recommended fix Moderate confidence

TIBCO Spotfire Server 7.14.1 or later (or Spotfire Analytics Platform for AWS 10.0.1 or later)

  1. Identify the currently deployed Spotfire Server or Spotfire Analytics Platform for AWS version using the TIBCO documentation or server administration console
  2. Download the latest TIBCO Spotfire Server version from the official TIBCO support portal (currently 7.14.1 or later stable release)
  3. Review the TIBCO Spotfire Server upgrade guide for your specific version
  4. Backup the existing Spotfire Server configuration, database, and deployment files
  5. Stop all Spotfire services before beginning the upgrade process
  6. Install the upgraded version following the TIBCO installation documentation
  7. Verify that authentication mechanisms are properly configured after upgrade
  8. Test the authentication flow to confirm the vulnerability is remediated
Caveat Review TIBCO release notes for version 7.14.1 for any configuration or feature changes; test thoroughly in non-production environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Spotfire Analytics Platform For Aws Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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 locally
dbcve dependency scanner

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