dbcve.org
Spotfire Analytics Platform For AwsApplication · Tibco

CVE-2019-17336

MEDIUM · 6.5 CVSS v3.1 Published 2019-12-17
Fix available
A fix is available. Upgrade to after 7.11.7 or later.
See remediation →
71/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 Data access layer component of TIBCO Software Inc.'s TIBCO Spotfire Analytics Platform for AWS Marketplace and TIBCO Spotfire Server contains multiple vulnerabilities that theoretically allow an attacker access to information that can lead to obtaining credentials used to access Spotfire data sources. The attacker would need privileges to save a Spotfire file to the library, and only applies in a situation where NTLM credentials, or a credentials profile is in use. Affected releases are TIBCO Software Inc.'s TIBCO Spotfire Analytics Platform for AWS Marketplace: version 10.6.0 and TIBCO Spotfire Server: versions 7.11.7 and below, versions 7.12.0, 7.13.0, 7.14.0, 10.0.0, 10.0.1, 10.1.0, 10.2.0, 10.2.1, 10.3.0, 10.3.1, 10.3.2, 10.3.3, and 10.3.4, versions 10.4.0, 10.5.0, and 10.6.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 data access layer in TIBCO Spotfire Server contains vulnerabilities allowing authenticated users with library file-save privileges to potentially access sensitive credential information used for data source connections, specifically when NTLM credentials or credential profiles are configured.

MitigationRestrict library save permissions to minimize attack surface, avoid using NTLM credentials or credential profiles where possible, and upgrade to a patched version once available from TIBCO.

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.6.0
Spotfire ServerApplication
Affected:<= 7.11.7= 7.12.0= 7.13.0= 7.14.0= 10.0.0= 10.0.1= 10.1.0= 10.2.0= 10.2.1= 10.3.0= 10.3.1= 10.3.2

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 installed TIBCO Spotfire Server version
    Locate the Spotfire Server installation and check the version information (typically available in server logs, about page, or installation directory metadata). Compare against the affected versions: <= 7.11.7; 7.12.0; 7.13.0; 7.14.0; 10.0.0; 10.1.0; 10.2.0; 10.2.1; 10.3.0; 10.3.1; 10.3.2; 10.6.0
    Affected if The installed version matches any of the listed affected versions
  2. Verify library file-save privileges are configured
    Check the Spotfire Server configuration for library permissions, specifically whether any users or groups are granted library file-save or file-create privileges
    Affected if Any authenticated user (beyond administrators) has library file-save permissions enabled in the system
  3. Identify if NTLM authentication is configured for data sources
    Review data source connection configurations to determine if NTLM authentication is being used for any data connections
    Affected if NTLM credentials are configured for any data source connections in the Spotfire environment
  4. Check if credential profiles are in use
    Examine the Spotfire data access layer configuration for credential profiles (named credential sets used for authentication)
    Affected if Credential profiles are defined or active for any data source connections

A user is affected if their Spotfire Server version is in the affected list AND they have library file-save permissions enabled for non-admin users AND they use NTLM credentials or credential profiles for data sources.

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.11.7
Interim mitigation

Restrict library save permissions to minimize attack surface, avoid using NTLM credentials or credential profiles where possible, and upgrade to a patched version once available from TIBCO.

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-2019-17336 — 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-2019-17336 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