# CVE-2022-22771: TIBCO JasperReports Library Directory Traversal Vulnerability

> A directory traversal vulnerability in TIBCO JasperReports Server allows web server users to access contents of 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:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Mar 2022
- **Updated:** 17 Sep 2024
- **Also known as:** BIT-jasperreports-2022-22771, GHSA-g4m4-hxvm-28mq, UBUNTU-CVE-2022-22771

## What is CVE-2022-22771?

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

### Official description

The Server component of TIBCO Software Inc.'s TIBCO JasperReports Library, TIBCO JasperReports Library for ActiveMatrix BPM, TIBCO JasperReports Server, TIBCO JasperReports Server for AWS Marketplace, TIBCO JasperReports Server for ActiveMatrix BPM, and TIBCO JasperReports Server for Microsoft Azure 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: version 7.9.0, TIBCO JasperReports Library for ActiveMatrix BPM: version 7.9.0, TIBCO JasperReports Server: versions 7.9.0 and 7.9.1, TIBCO JasperReports Server for AWS Marketplace: versions 7.9.0 and 7.9.1, TIBCO JasperReports Server for ActiveMatrix BPM: versions 7.9.0 and 7.9.1, and TIBCO JasperReports Server for Microsoft Azure: version 7.9.1.

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

## Which versions are affected by CVE-2022-22771?

1 open source package ship an affected version, including jasperreports. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `jasperreports` | Bitnami | From 7.9.0 to 7.9.0 | None |

Products: Tibco Jasperreports Library, Tibco Jasperreports Server.

## How do I fix CVE-2022-22771?

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

## Is CVE-2022-22771 being exploited?

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

What it is: CVE-2022-22771 is a critical path traversal vulnerability in TIBCO JasperReports Library, published on 15 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-22771 in the wild and no public exploit code.

Affected packages and fixed versions:
- jasperreports (Bitnami): affected from 7.9.0 up to 7.9.0; no fix listed

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

## Sources

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

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