# CVE-2020-9409: TIBCO JasperReports Server Fails To Enforce Access Restrictions

> Unauthenticated attackers can bypass access restrictions to gain superuser privileges on TIBCO JasperReports Server administrative interfaces.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 May 2020
- **Updated:** 17 Sep 2024
- **Also known as:** BIT-jasperreports-2020-9409, GHSA-j2v4-xwh5-47fc

## What is CVE-2020-9409?

CVE-2020-9409 is a critical authentication bypass vulnerability in TIBCO JasperReports Server, published on 20 May 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The administrative UI component of TIBCO Software Inc.'s TIBCO JasperReports Server, TIBCO JasperReports Server for AWS Marketplace, and TIBCO JasperReports Server for ActiveMatrix BPM contains a vulnerability that theoretically allows an unauthenticated attacker to obtain the permissions of a JasperReports Server "superuser" for the affected systems. The attacker can theoretically exploit the vulnerability consistently, remotely, and without authenticating. Affected releases are TIBCO Software Inc.'s TIBCO JasperReports Server: versions 7.1.1 and below, TIBCO JasperReports Server for AWS Marketplace: versions 7.1.1 and below, and TIBCO JasperReports Server for ActiveMatrix BPM: versions 7.1.1 and below.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2020-9409?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `jasperreports` | Bitnami | All versions | 7.1.1 |

Products: Oracle Retail Order Broker, Tibco Jasperreports Server.

## How do I fix CVE-2020-9409?

Upgrade jasperreports to 7.1.1 or later.

## Is CVE-2020-9409 being exploited?

There is no known exploitation of CVE-2020-9409 in the wild and no public exploit code.

## Other vulnerabilities in TIBCO JasperReports Server

- [CVE-2016-3565](https://insights.sbomify.com/CVE-2016-3565/): Other in n/a (high 7.6)
- [CVE-2020-9410](https://insights.sbomify.com/CVE-2020-9410/): TIBCO JasperReports Library (high 7.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-9409 and fix it if it is affected.

What it is: CVE-2020-9409 is a critical authentication bypass vulnerability in TIBCO JasperReports Server, published on 20 May 2020. 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-2020-9409 in the wild and no public exploit code.

Affected packages and fixed versions:
- jasperreports (Bitnami): affected all versions; fixed in 7.1.1

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

## Sources

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

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