# CVE-2017-5533: TIBCO JasperReports Server credentials disclosure

> Remote attackers can access sensitive configuration files and credentials due to improper access controls in the server content cache.

- **Severity:** Critical 9.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Nov 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-27wc-fr9j-8x58, UBUNTU-CVE-2017-5533

## What is CVE-2017-5533?

CVE-2017-5533 is a critical vulnerability in TIBCO JasperReports Server, published on 15 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the server content cache of TIBCO JasperReports Server, TIBCO JasperReports Server Community Edition, TIBCO JasperReports Server for ActiveMatrix BPM, TIBCO Jaspersoft for AWS with Multi-Tenancy, and TIBCO Jaspersoft Reporting and Analytics for AWS contains a vulnerability which fails to prevent remote access to all the contents of the web application, including key configuration files. Affected releases are TIBCO JasperReports Server 6.4.0, TIBCO JasperReports Server Community Edition 6.4.0, TIBCO JasperReports Server for ActiveMatrix BPM 6.4.0, TIBCO Jaspersoft for AWS with Multi-Tenancy 6.4.0, TIBCO Jaspersoft Reporting and Analytics for AWS 6.4.0.

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

It affects 3 products.


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

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

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

## Is CVE-2017-5533 being exploited?

There is no known exploitation of CVE-2017-5533 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-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)
- [CVE-2021-35495](https://insights.sbomify.com/CVE-2021-35495/): TIBCO JasperReports FTP Password exposed (critical 9.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-5533 is a critical vulnerability in TIBCO JasperReports Server, published on 15 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-5533 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-5533/ (Markdown: https://insights.sbomify.com/CVE-2017-5533/index.md)
```

## Sources

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

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