CVE-2019-17330
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 multiple vulnerabilities that theoretically allow authenticated users to perform stored cross-site scripting (XSS) attacks, and unauthenticated users to perform reflected cross-site scripting attacks. Affected releases are TIBCO Software Inc.'s TIBCO EBX: versions up to and including 5.8.1.fixR, versions 5.9.3, 5.9.4, 5.9.5, and 5.9.6.
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 EBX web server contains stored and reflected XSS vulnerabilities. Authenticated users can inject malicious scripts that persist (stored XSS), while unauthenticated users can trigger reflective attacks via crafted URLs. The 9.6 CVSS reflects the ease of exploitation and potential for session hijacking, credential theft, or malicious action execution 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<= 5.8.1= 5.8.1= 5.9.3= 5.9.4= 5.9.5= 5.9.6CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
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 version through the product's about page, version manifest file within the installation directory, or by accessing the /about endpoint on the web interface if availableAffected if The installed version is 5.8.1, 5.9.3, 5.9.4, 5.9.5, 5.9.6, or any version <= 5.8.1
-
Confirm EBX web server is accessibleVerify the EBX web application is running and accessible by accessing the configured web URL and port (commonly 8080 or 8443)Affected if The EBX web interface is exposed and responds to HTTP requests
-
Check for stored XSS injection pointsReview application input fields and forms where user-supplied data is stored and displayed back, looking for lack of output encoding in the application responseAffected if User-supplied data is rendered without proper sanitization and persists in the application
-
Check for reflected XSS via URL parametersTest URL parameters and query strings by submitting special characters and observing if they are reflected in the response without encodingAffected if URL parameters are reflected in the page response without proper encoding
If the installed Tibco Ebx version falls within 5.8.1 through 5.9.6 (or <=5.8.1) and the web interface is accessible without input validation or output encoding, the environment is affected by CVE-2019-17330.
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 EBX to vendor-provided patched version; implement output encoding, input validation, and Content Security Policy headers as compensating controls until patching is feasible.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-17330 — 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-17330 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