# CVE-2020-9410: TIBCO JasperReports Library

> Attackers can inject HTML into reports using Fusion Charts to execute scripts in viewers' browsers, potentially taking over accounts or executing code.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 20 May 2020
- **Updated:** 16 Sep 2024
- **Also known as:** BIT-jasperreports-2020-9410, GHSA-jcfp-678f-37q2

## What is CVE-2020-9410?

CVE-2020-9410 is a high-severity cross-site scripting vulnerability in TIBCO JasperReports Library, published on 20 May 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The report generator component of TIBCO Software Inc.'s TIBCO JasperReports Library, TIBCO JasperReports Library for ActiveMatrix BPM, TIBCO JasperReports Server, TIBCO JasperReports Server for AWS Marketplace, and TIBCO JasperReports Server for ActiveMatrix BPM contains a vulnerability that theoretically allows an attacker to exploit HTML injection to gain full control of a web interface containing the output of the report generator component with the privileges of any user that views the affected report(s). The attacker can theoretically exploit this vulnerability when other users view a maliciously generated report, where those reports use Fusion Charts and a data source with contents controlled by the attacker. Affected releases are TIBCO Software Inc.'s TIBCO JasperReports Library: versions 7.1.1 and below, versions 7.2.0 and 7.2.1, version 7.3.0, version 7.5.0, TIBCO JasperReports Library for ActiveMatrix BPM: versions 7.1.1 and below, TIBCO JasperReports Server: versions 7.1.1 and below, version 7.2.0, version 7.5.0, TIBCO JasperReports Server for AWS Marketplace: versions 7.5.0 and below, and TIBCO JasperReports Server for ActiveMatrix BPM: versions 7.1.1 and below.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

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


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

Products: Oracle Retail Order Broker, Tibco Jasperreports Library, Tibco Jasperreports Server.

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

Upgrade jasperreports to 7.5.0 or later.

## Is CVE-2020-9410 being exploited?

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

## Other vulnerabilities in TIBCO JasperReports Library

- [CVE-2020-9409](https://insights.sbomify.com/CVE-2020-9409/): TIBCO JasperReports Server Fails To Enforce Access Restrictions (critical 9.8)
- [CVE-2016-3565](https://insights.sbomify.com/CVE-2016-3565/): Other in n/a (high 7.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-9410 is a high-severity cross-site scripting vulnerability in TIBCO JasperReports Library, published on 20 May 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-9410 in the wild and no public exploit code.

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

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

## Sources

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

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