# CVE-2018-18809: TIBCO JasperReports Library Directory Traversal

> Attackers can exploit a directory traversal flaw in TIBCO JasperReports Server to access sensitive files on the host system.

- **Severity:** Critical 9.9 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 29 Dec 2022 (CISA KEV)
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Mar 2019
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-2qh3-cx4w-cf3x

## What is CVE-2018-18809?

CVE-2018-18809 is a critical path traversal vulnerability in TIBCO JasperReports Library, published on 7 Mar 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The default server implementation of TIBCO Software Inc.'s TIBCO JasperReports Library, TIBCO JasperReports Library Community Edition, TIBCO JasperReports Library for ActiveMatrix BPM, 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 directory-traversal vulnerability that may theoretically allow web server users to access contents of the host system. Affected releases are TIBCO Software Inc.'s TIBCO JasperReports Library: versions up to and including 6.3.4; 6.4.1; 6.4.2; 6.4.21; 7.1.0; 7.2.0, TIBCO JasperReports Library Community Edition: versions up to and including 6.7.0, TIBCO JasperReports Library for ActiveMatrix BPM: versions up to and including 6.4.21, 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 6.4.3; 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, TIBCO Jaspersoft Reporting and Analytics for AWS: versions up to and including 7.1.0.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 4 products.


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

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

No fix has been published for CVE-2018-18809 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 19 Jan 2023.

## Is CVE-2018-18809 being exploited?

Yes. Attackers have exploited CVE-2018-18809 in the wild since at least 29 Dec 2022.

Public exploit code:

- TIBCO JasperReports Library - Directory Traversal (nuclei): http/cves/2018/CVE-2018-18809.yaml

## Other vulnerabilities in TIBCO JasperReports Library

- [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)
- [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-18809 and fix it if it is affected.

What it is: CVE-2018-18809 is a critical path traversal vulnerability in TIBCO JasperReports Library, published on 7 Mar 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2018-18809 in the wild since at least 29 Dec 2022.

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-18809/ (Markdown: https://insights.sbomify.com/CVE-2018-18809/index.md)
```

## Sources

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

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