# CVE-2018-5429: TIBCO JasperReports Library Code Sandboxing Problem

> Attackers can execute arbitrary code via malicious scripting in analytic reports within TIBCO JasperReports products.

- **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:** 17 Apr 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-6524-6266-mqf2, UBUNTU-CVE-2018-5429

## What is CVE-2018-5429?

CVE-2018-5429 is a high-severity code injection vulnerability in TIBCO JasperReports Library, published on 17 Apr 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability in the report scripting component of TIBCO Software Inc.'s TIBCO JasperReports Server, TIBCO JasperReports Server Community Edition, TIBCO JasperReports Server for ActiveMatrix BPM, TIBCO JasperReports Library, TIBCO JasperReports Library Community Edition, TIBCO JasperReports Library for ActiveMatrix BPM, TIBCO Jaspersoft for AWS with Multi-Tenancy, TIBCO Jaspersoft Reporting and Analytics for AWS, TIBCO Jaspersoft Studio, TIBCO Jaspersoft Studio Community Edition, and TIBCO Jaspersoft Studio for ActiveMatrix BPM may allow analytic reports that contain scripting to perform arbitrary code execution. Affected releases include TIBCO Software Inc.'s TIBCO JasperReports Server: versions up to and including 6.2.4; 6.3.0; 6.3.2;6.3.3; 6.4.0; 6.4.2, TIBCO JasperReports Server Community Edition: versions up to and including 6.4.2, TIBCO JasperReports Server for ActiveMatrix BPM: versions up to and including 6.4.2, TIBCO JasperReports Library: versions up to and including 6.2.4; 6.3.0; 6.3.2; 6.3.3; 6.4.0; 6.4.1; 6.4.2, TIBCO JasperReports Library Community Edition: versions up to and including 6.4.3, TIBCO JasperReports Library for ActiveMatrix BPM: versions up to and including 6.4.2, TIBCO Jaspersoft for AWS with Multi-Tenancy: versions up to and including 6.4.2, TIBCO Jaspersoft Reporting and Analytics for AWS: versions up to and including 6.4.2, TIBCO Jaspersoft Studio: versions up to and including 6.2.4; 6.3.0; 6.3.2; 6.3.3; 6.4.0; 6.4.2, TIBCO Jaspersoft Studio Community Edition: versions up to and including 6.4.3, TIBCO Jaspersoft Studio for ActiveMatrix BPM: versions up to and including 6.4.2.

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

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-2018-5429?

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

## Is CVE-2018-5429 being exploited?

There is no known exploitation of CVE-2018-5429 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-2017-5532](https://insights.sbomify.com/CVE-2017-5532/): TIBCO JasperReports persistent cross site scripting (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-5429 and fix it if it is affected.

What it is: CVE-2018-5429 is a high-severity code injection vulnerability in TIBCO JasperReports Library, published on 17 Apr 2018. 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-5429 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-2018-5429/ (Markdown: https://insights.sbomify.com/CVE-2018-5429/index.md)
```

## Sources

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

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