CVE-2019-17335
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 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 data cached from a data source, or a portion of a data source, that the attacker should not have access to. The attacker would need privileges to save a Spotfire file to the library. 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 · high confidenceTIBCO Spotfire Analytics Platform's data access layer contains an insecure direct object reference or improper access control vulnerability allowing authenticated users with library save privileges to access cached data from data sources they shouldn't have permission to view. This is an information disclosure flaw in how the platform caches and serves data through its library system.
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= 10.6.0<= 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.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Spotfire Server versionCheck the server's About page in the Spotfire Administrator tool, or run 'tsm version' command if using TIBCO Server Management, or inspect the installation metadata file. Compare the version number against the affected ranges: <= 7.11.7, 7.12.0, 7.13.0, 7.14.0, 10.0.0-10.3.2, or 10.6.0 for AWS.Affected if The installed version matches any of the listed affected versions or falls within the affected ranges.
-
Confirm Spotfire Library is enabledLog into Spotfire Server as an administrator and navigate to the Configuration tool, then check the Library settings. The Library system must be active for this vulnerability to be exploitable.Affected if The Library feature is enabled and users have been granted library save privileges.
-
Identify data sources with cached dataIn Spotfire Administrator, review the Library content and look for any analysis files or data connections that have cached data. Check which data sources are configured and whether they contain sensitive information that should be restricted.Affected if There are data sources configured with cached data accessible through the Library system.
-
Audit user privileges in the LibraryIn Spotfire Administrator, review the Users and Groups permissions. Specifically check which users or groups have 'Library Save' or 'Library Write' privileges, as these permissions are required for exploitation.Affected if Users other than administrators have library save privileges and there are data sources they should not have access to.
You are affected if your installed Spotfire Server version matches any of the affected versions AND the Library feature is enabled with users having save privileges on data sources they should not access.
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 TIBCO Spotfire Server to a version beyond 10.6.0 or apply vendor-supplied patches. Limit user privileges to the library and review data source access controls in the meantime.
- 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-2019-17335 — 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-2019-17335 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