CVE-2017-5536
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 GridServer Broker, and GridServer Director components of TIBCO Software Inc. TIBCO DataSynapse GridServer Manager contain vulnerabilities which may allow an authenticated user to perform cross-site scripting (XSS). In addition, an authenticated user could be a victim of a cross-site request forgery (CSRF) attack. Affected releases include TIBCO Software Inc.'s TIBCO DataSynapse GridServer Manager: versions up to and including 5.1.3; 6.0.0; 6.0.1; 6.0.2; 6.1.0; 6.1.1; and 6.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 confidenceTIBCO DataSynapse GridServer Manager contains stored XSS vulnerabilities in the GridServer Broker and GridServer Director components, allowing authenticated users to inject malicious scripts. Additionally, the application lacks proper CSRF protection, enabling attackers to craft malicious requests that authenticated users unknowingly execute.
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.1.3= 6.0.0= 6.0.1= 6.0.2= 6.1.0= 6.1.1= 6.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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/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 GridServer Manager installationLocate the TIBCO DataSynapse GridServer Manager installation directory and look for version information in product documentation, installation files, or the product's built-in version display. Common locations include the product's bin directory or welcome page.Affected if The installed version matches <= 5.1.3, 6.0.0, 6.0.1, 6.0.2, 6.1.0, 6.1.1, or 6.2.0
-
Confirm GridServer Broker web interface is accessibleAccess the GridServer Broker web management console URL (typically on port 8080 or 8443) and verify the application is reachable.Affected if The Broker web interface is accessible without additional authentication barriers beyond the application login
-
Verify authentication is required for the web interfaceNavigate to the GridServer Manager login page and confirm that user credentials are required to access the Broker or Director components.Affected if The web interface accepts authentication but does not implement CSRF token validation on state-changing operations
-
Check if user-supplied input is accepted in Broker or DirectorLog into the GridServer Manager web console and identify input fields in the Broker or Director management pages where users can submit custom values (such as configuration names, descriptions, or custom parameters).Affected if Input fields in these components do not appear to sanitize or encode special characters before storage or display
You are affected if your GridServer Manager version falls within the listed affected versions and the Broker or Director web components are accessible to authenticated users without CSRF protection on sensitive operations.
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 dataImplement input validation and output encoding for all user-supplied data to prevent XSS attacks. Deploy CSRF tokens (synchronizer token pattern) on state-changing operations and validate the Origin/Referer headers.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5536 — 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-2017-5536 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