# CVE-2017-5528: TIBCO JasperReports Server cross-site vulnerabilities

> Authorized users can exploit XSS and CSRF vulnerabilities in TIBCO JasperReports Server to disclose sensitive information.

- **Severity:** Medium 5.7 (`CVSS:3.0/A:N/AC:L/AV:N/C:H/I:N/PR:L/S:U/UI:R`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Jun 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-899x-3fcr-8p3x, UBUNTU-CVE-2017-5528

## What is CVE-2017-5528?

CVE-2017-5528 is a medium-severity cross-site scripting vulnerability in TIBCO JasperReports Server, published on 29 Jun 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Multiple JasperReports Server components contain vulnerabilities which may allow authorized users to perform cross-site scripting (XSS) and cross-site request forgery (CSRF) attacks.  The impact of this vulnerability includes the theoretical disclosure of sensitive information.  Affects TIBCO JasperReports Server (versions 6.1.1 and below, 6.2.0, 6.2.1, and 6.3.0), TIBCO JasperReports Server Community Edition (versions 6.3.0 and below), TIBCO JasperReports Server for ActiveMatrix BPM (versions 6.2.0 and below), TIBCO Jaspersoft for AWS with Multi-Tenancy (versions 6.2.0 and below), and TIBCO Jaspersoft Reporting and Analytics for AWS (versions 6.2.0 and below).

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2017-5528?

It affects 3 products.


Products: Tibco Jasperreports Server, Tibco Jaspersoft, Tibco Jaspersoft Reporting and Analytics.

## How do I fix CVE-2017-5528?

No fix has been published for CVE-2017-5528 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-5528 being exploited?

There is no known exploitation of CVE-2017-5528 in the wild and no public exploit code.

## Other vulnerabilities in TIBCO JasperReports Server

- [CVE-2018-5430](https://insights.sbomify.com/CVE-2018-5430/): TIBCO JasperReports Server Information Disclosure (high 7.7, exploited in the wild)
- [CVE-2018-18815](https://insights.sbomify.com/CVE-2018-18815/): TIBCO JasperReports Server User Information Disclosure (critical 10.0)
- [CVE-2017-5533](https://insights.sbomify.com/CVE-2017-5533/): TIBCO JasperReports Server credentials disclosure (critical 9.3)
- [CVE-2022-41561](https://insights.sbomify.com/CVE-2022-41561/): TIBCO JasperReports Server RCE Vulnerability (critical 9.1)
- [CVE-2022-41563](https://insights.sbomify.com/CVE-2022-41563/): TIBCO JasperReports Server Stored XSS Vulnerability (critical 9.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-5528 and fix it if it is affected.

What it is: CVE-2017-5528 is a medium-severity cross-site scripting vulnerability in TIBCO JasperReports Server, published on 29 Jun 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-5528 in the wild and no public exploit code.

Affected product: TIBCO JasperReports Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-5528/ (Markdown: https://insights.sbomify.com/CVE-2017-5528/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-5528
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-5528
- OSV: https://osv.dev/vulnerability/CVE-2017-5528

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-5528/
Summaries are generated and may contain mistakes; the official description above is the record.