# CVE-2018-18808: TIBCO JasperReports Server Privilege Escalation Via Race Condition

> A race condition in TIBCO JasperReports Server allows users with domain save privileges to escalate to superuser access.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Mar 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-85xr-j783-4jm2

## What is CVE-2018-18808?

CVE-2018-18808 is a high-severity vulnerability in TIBCO JasperReports Server, published on 7 Mar 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The domain management component of TIBCO Software Inc.'s 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 race-condition vulnerability that may allow any users with domain save privileges to gain superuser privileges. Affected releases are TIBCO Software Inc.'s TIBCO JasperReports Server: versions up to and including 6.3.4; 6.4.0; 6.4.1; 6.4.2; 6.4.3; 7.1.0, TIBCO JasperReports Server Community Edition: versions up to and including 7.1.0, TIBCO JasperReports Server for ActiveMatrix BPM: versions up to and including 6.4.3, TIBCO Jaspersoft for AWS with Multi-Tenancy: versions up to and including 7.1.0, and TIBCO Jaspersoft Reporting and Analytics for AWS: versions up to and including 7.1.0.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2018-18808?

It affects 3 products.


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

## How do I fix CVE-2018-18808?

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

## Is CVE-2018-18808 being exploited?

There is no known exploitation of CVE-2018-18808 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-2018-18808 and fix it if it is affected.

What it is: CVE-2018-18808 is a high-severity vulnerability in TIBCO JasperReports Server, published on 7 Mar 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-18808 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-2018-18808/ (Markdown: https://insights.sbomify.com/CVE-2018-18808/index.md)
```

## Sources

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

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