CVE-2019-17333
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 EBX contains a vulnerability that theoretically allows authenticated users to perform stored cross-site scripting (XSS) attacks. Affected releases are TIBCO Software Inc.'s TIBCO EBX: versions 5.8.1.fixS and below, versions 5.9.3, 5.9.4, 5.9.5, 5.9.6, and 5.9.7.
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 confidenceTIBCO EBX Web server component contains a stored cross-site scripting (XSS) vulnerability that can be exploited by authenticated users. The vulnerability allows injection of malicious scripts into web content that is stored on the server and presented to other users, potentially enabling session hijacking or credential theft.
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< 5.8.1>= 5.9.3, <= 5.9.7= 5.8.1CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 TIBCO EBX versionLocate the EBX installation directory and check the version file or startup logs. Common locations include the version.txt file in the installation root, or the version information displayed in the EBX web interface footer.Affected if The installed version is < 5.8.1, = 5.8.1, or >= 5.9.3 AND <= 5.9.7.
-
Confirm web server component is enabledVerify that the EBX web server (typically running on port 8080 or 8443) is accessible and serving the EBX application. Check server configuration files for web component settings.Affected if The EBX web interface is accessible without additional isolation measures.
-
Verify user authentication is configuredReview the EBX authentication settings in the configuration files (such as authentication.xml or security configuration) to determine if user authentication is enabled.Affected if User authentication is enabled, which is required for authenticated users to exploit the stored XSS.
-
Check for recent security updatesReview the EBX patch history or contact TIBCO support to confirm whether the vendor patch for this CVE has been applied.Affected if The patch for CVE-2019-17333 has not been applied to the installation.
Your environment is affected if TIBCO EBX is running a version in the vulnerable range (< 5.8.1, 5.8.1, or 5.9.3 through 5.9.7) with the web component accessible and user authentication enabled.
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 data5.8.1
Apply the vendor-supplied patch or upgrade to a fixed version of TIBCO EBX beyond 5.9.7. As a temporary measure, implement input validation and output encoding, and consider WAF rules to detect and block XSS payloads.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-17333 — 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-17333 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