dbcve.org
Spotfire Analytics Platform For AwsApplication · Tibco

CVE-2018-5436

HIGH · 8.8 CVSS v3.0 Published 2018-06-27
Fix available
A fix is available. Upgrade to after 7.12.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 Spotfire server component of TIBCO Software Inc.'s TIBCO Spotfire Analytics Platform for AWS Marketplace, and TIBCO Spotfire Server contain multiple vulnerabilities that may allow for the disclosure of information, including user and data source credentials. Affected releases are TIBCO Software Inc.'s TIBCO Spotfire Analytics Platform for AWS Marketplace: versions up to and including 7.12.0, TIBCO Spotfire Server: versions up to and including 7.8.1; 7.9.0; 7.10.0; 7.11.0; 7.12.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

The TIBCO Spotfire Server component contains multiple vulnerabilities that allow disclosure of sensitive information, specifically user credentials and data source credentials. This is an information disclosure vulnerability in the Spotfire server's authentication or credential storage mechanisms.

MitigationUpgrade TIBCO Spotfire Server to a version beyond 7.12.0, or apply vendor-provided patches. If immediate patching is not feasible, audit credential storage mechanisms and implement additional access controls around sensitive credential 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
Spotfire Analytics Platform For AwsApplication
Affected:<= 7.12.0
Spotfire ServerApplication
Affected:<= 7.8.1= 7.9.0= 7.10.0= 7.11.0= 7.12.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:L/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 Spotfire Server installation and version
    Locate the Spotfire Server installation directory and check the version. On Windows, this is typically in the Spotfire Server installation folder. Look for a version file or check the server's about page in the administration tool. The version is usually displayed in the Spotfire Server administration interface or can be found in version-related files in the installation directory.
    Affected if The installed version is 7.12.0 or earlier, or matches 7.8.1, 7.9.0, 7.10.0, 7.11.0, or 7.12.0 specifically.
  2. Locate credential configuration files
    Identify where Spotfire stores credentials. Check the configuration directory (typically <installation>/tomcat/spotfire-bin/conf/ or <installation>/spotfireserver/ configuration folders). Look for files related to authentication configuration, datasource connections, and credential storage such as bootstrap.xml, spotfire-config.xml, or similar configuration files that may contain stored credentials.
    Affected if Configuration files containing plaintext credentials or easily reversible credential encodings are found in the configuration directory.
  3. Verify access controls on sensitive configuration files
    Check file system permissions on the configuration directory and credential-containing files. On Windows, use icacls or File Properties > Security. On Linux, use ls -la to check permissions. Ensure that only authorized administrators and the service account have read access.
    Affected if Files containing credentials are readable by non-administrative users or have overly permissive file permissions (e.g., world-readable).
  4. Review authentication and credential storage configuration
    Examine the Spotfire Server configuration for how credentials are stored. Check the authentication configuration files for the method used (e.g., LDAP, internal database). Look for any configuration indicating credentials are stored in an insecure manner or transmitted without proper encryption.
    Affected if The server is configured to use internal authentication with credentials stored in a manner that allows extraction, or credential storage mechanisms lack encryption.

A user is affected if the installed TIBCO Spotfire Server version is 7.12.0 or earlier (specifically 7.8.1, 7.9.0, 7.10.0, 7.11.0, or 7.12.0) AND sensitive credential data is accessible through configuration files with insufficient access controls.

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.

From vendor data
Upgrade available Upgrade to a release after 7.12.0
Interim mitigation

Upgrade TIBCO Spotfire Server to a version beyond 7.12.0, or apply vendor-provided patches. If immediate patching is not feasible, audit credential storage mechanisms and implement additional access controls around sensitive credential data.

Fix this in Spotfire Analytics Platform For Aws Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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