# CVE-2017-5532: TIBCO JasperReports persistent cross site scripting

> Authorized users can perform persistent cross-site scripting attacks in the report renderer component of TIBCO JasperReports products.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N`)
- **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:** 15 Nov 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-cwm8-8754-76qc, UBUNTU-CVE-2017-5532

## What is CVE-2017-5532?

CVE-2017-5532 is a medium-severity cross-site scripting vulnerability in TIBCO JasperReports Library, published on 15 Nov 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

A vulnerability in the report renderer component of TIBCO JasperReports Server, TIBCO JasperReports Server Community Edition, TIBCO JasperReports Server for ActiveMatrix BPM, TIBCO JasperReports Library, TIBCO JasperReports Library for ActiveMatrix BPM, TIBCO Jaspersoft for AWS with Multi-Tenancy, TIBCO Jaspersoft Reporting and Analytics for AWS, TIBCO Jaspersoft Studio, and TIBCO Jaspersoft Studio for ActiveMatrix BPM may allow a subset of authorized users to perform persistent cross-site scripting (XSS) attacks. Affected releases are TIBCO JasperReports Server 6.2.3 and below; 6.3.0; 6.3.1; 6.3.2; 6.4.0, TIBCO JasperReports Server Community Edition 6.4.0 and below, TIBCO JasperReports Server for ActiveMatrix BPM 6.4.0 and below, TIBCO JasperReports Library 6.2.3 and below; 6.3.0; 6.3.1; 6.3.2; 6.4.0; 6.4.1, TIBCO JasperReports Library for ActiveMatrix BPM 6.4.1 and below, TIBCO Jaspersoft for AWS with Multi-Tenancy 6.4.0 and below, TIBCO Jaspersoft Reporting and Analytics for AWS 6.4.0 and below, TIBCO Jaspersoft Studio 6.2.3 and below; 6.3.0; 6.3.1; 6.3.2; 6.4.0, and TIBCO Jaspersoft Studio for ActiveMatrix BPM 6.4.0 and below.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 5 products.


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

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

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

## Is CVE-2017-5532 being exploited?

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

## Other vulnerabilities in TIBCO JasperReports Library

- [CVE-2018-18809](https://insights.sbomify.com/CVE-2018-18809/): TIBCO JasperReports Library Directory Traversal (critical 9.9, exploited in the wild)
- [CVE-2022-22771](https://insights.sbomify.com/CVE-2022-22771/): TIBCO JasperReports Library Directory Traversal Vulnerability (critical 9.9)
- [CVE-2018-5429](https://insights.sbomify.com/CVE-2018-5429/): TIBCO JasperReports Library Code Sandboxing Problem (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-5532 is a medium-severity cross-site scripting vulnerability in TIBCO JasperReports Library, published on 15 Nov 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-5532 in the wild and no public exploit code.

Affected product: TIBCO JasperReports Library. 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-5532/ (Markdown: https://insights.sbomify.com/CVE-2017-5532/index.md)
```

## Sources

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

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