CVE-2019-11205
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 web server component of TIBCO Software Inc.'s TIBCO Spotfire Analytics Platform for AWS Marketplace, and TIBCO Spotfire Server contains vulnerabilities that theoretically allow reflected cross-site scripting (XSS) attacks. Affected releases are TIBCO Software Inc.'s TIBCO Spotfire Analytics Platform for AWS Marketplace: 7.14.0; 7.14.1; 10.0.0; 10.0.1; 10.1.0; 10.2.0, and TIBCO Spotfire Server: 7.14.0; 10.0.0; 10.0.1; 10.1.0; 10.2.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 confidenceReflected XSS vulnerability in the web server component of TIBCO Spotfire Analytics Platform and TIBCO Spotfire Server. User-supplied input is returned in server responses without proper sanitization, allowing execution of malicious scripts in user browsers.
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= 7.14.0= 7.14.1= 10.0.0= 10.0.1= 10.1.0= 10.2.0= 7.14.0= 10.0.0= 10.0.1= 10.1.0= 10.2.0CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 TIBCO Spotfire Server versionAccess the server administration interface or check the installation directory for version information. On the server, look for version metadata in the installation folder or check the 'About' page of the Spotfire web client.Affected if The installed version matches 7.14.0, 7.14.1, 10.0.0, 10.1.0, or 10.2.0 for Spotfire Server, or matches the same versions for Spotfire Analytics Platform for AWS.
-
Confirm the web server component is enabledVerify that the Spotfire web server (TIBCO Spotfire Server web tier) is running and accessible. Check if HTTP/HTTPS ports for the web interface are listening and responding.Affected if The web server component is active and exposed on network-accessible ports.
-
Check for unauthenticated web endpointsReview the Spotfire web application for endpoints that accept user-supplied input and return it in server responses without encoding. Common areas include search parameters, navigation parameters, or form inputs.Affected if The web application reflects user-supplied input directly in HTML responses without sanitization.
-
Compare installed version against affected rangesDocument the exact version number from step 1 and cross-reference it against the affected versions: 7.14.0, 7.14.1, 10.0.0, 10.1.0, and 10.2.0.Affected if The installed version exactly matches one of the listed affected versions.
A user is affected if they are running TIBCO Spotfire Server or Spotfire Analytics Platform for AWS versions 7.14.0, 7.14.1, 10.0.0, 10.1.0, or 10.2.0 with the web server component accessible to users.
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 dataApply vendor-supplied patches for affected versions (7.14.0-7.14.1, 10.0.0-10.2.0). Implement input validation and output encoding as defense-in-depth measures.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11205 — 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-11205 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