dbcve.org
Spotfire Analytics Platform For AwsApplication · Tibco

CVE-2018-18812

MEDIUM · 5.3 CVSS v3.0 Published 2019-01-16
Fix available
A fix is available. Upgrade to after 10.0.0 or later.
See remediation →
59/100
Remediation priority · Elevated
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 Library component of TIBCO Software Inc.'s TIBCO Spotfire Analytics Platform for AWS Marketplace, and TIBCO Spotfire Server contains a vulnerability that might theoretically fail to restrict users with read-only access from modifying files stored in the Spotfire Library, only when the Spotfire Library is configured to use external storage. Affected releases are TIBCO Software Inc.'s 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; 10.0.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 Spotfire Library component contains an access control flaw where users with read-only permissions might be able to modify files stored in the library when it is configured to use external storage, violating the intended permission model.

MitigationReview the Spotfire Library configuration to ensure proper access controls are enforced regardless of storage type, and apply vendor patches when available. Consider restricting external storage configuration until patches are applied.

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= 10.0.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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/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 checks

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

  1. Identify your Spotfire product and version
    Locate the Spotfire Server installation directory and check the version file or use the Spotfire Server configuration tool (tss) to query the version. On the server, you can typically find version info in the installation logs or by accessing the server diagnostics page.
    Affected if The installed version matches any of the affected versions: 10.0.0 or lower for AWS version, or any of 7.10.1 and below, 7.11.0, 7.11.1, 7.12.0, 7.13.0, 7.14.0, or 10.0.0 for Spotfire Server.
  2. Determine if Library external storage is configured
    Access the Spotfire Server configuration tool (or check the library configuration files in the deployment area). Look for Library configuration settings that specify external storage locations such as AWS S3, Azure Blob Storage, or network file shares.
    Affected if The Library component is configured to use external storage (cloud storage or network share) rather than the default local file storage.
  3. Verify the storage configuration method
    In the Spotfire Server configuration console, navigate to Library and Archives settings. Check the storage backend configuration to confirm if an external storage provider is selected.
    Affected if The storage type is set to anything other than the default local storage (for example, if it shows S3, Azure Blob, or a custom external path).
  4. Review Library permission assignments
    In Spotfire Administrator, navigate to Library permissions for user groups. Check which groups have read-only access versus read-write or modify permissions.
    Affected if There exist users or groups in the environment with only read-only permissions to Library contents, and external storage is enabled.

You are affected if you are running a vulnerable Spotfire version AND have the Library configured to use external storage, allowing read-only users potential unauthorized modification access.

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 10.0.0
Interim mitigation

Review the Spotfire Library configuration to ensure proper access controls are enforced regardless of storage type, and apply vendor patches when available. Consider restricting external storage configuration until patches are applied.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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