# CVE-2019-17091: Cross-site Scripting in Eclipse Mojarra

> Reflected XSS in Eclipse Mojarra allows attackers to execute arbitrary scripts via mishandled client window fields.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 2 Oct 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rjhx-c9qh-qh8f

## What is CVE-2019-17091?

CVE-2019-17091 is a medium-severity cross-site scripting vulnerability in Oracle Application Testing Suite, published on 2 Oct 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

faces/context/PartialViewContextImpl.java in Eclipse Mojarra, as used in Mojarra for Eclipse EE4J before 2.3.10 and Mojarra JavaServer Faces before 2.2.20, allows Reflected XSS because a client window field is mishandled.

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

## Which versions are affected by CVE-2019-17091?

4 open source packages ship an affected version, including org.glassfish:jakarta.faces and org.glassfish:javax.faces. It affects 23 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.glassfish:jakarta.faces` | Maven | All versions | 2.3.10 |
| `org.glassfish:jakarta.faces` | Maven | All versions | 2.3.10 |
| `org.glassfish:javax.faces` | Maven | All versions | 2.2.20 |
| `org.glassfish:javax.faces` | Maven | All versions | 2.2.20 |

Products: Eclipse Mojarra, Oracle Application Testing Suite, Oracle Banking Enterprise Product Manufacturing, Oracle Communications Diameter Signaling Router, Oracle Communications Network Integrity, Oracle Communications Unified Inventory Management, Oracle Enterprise Data Quality, Oracle Health Sciences Information Manager, Oracle Healthcare Data Repository, Oracle Mojarra Javaserver Faces, Oracle Primavera P6 Enterprise Project Portfolio Management, Oracle Rapid Planning, Oracle Retail Advanced Inventory Planning, Oracle Retail Assortment Planning, Oracle Retail Bulk Data Integration, Oracle Retail Financial Integration, Oracle Retail Integration Bus, Oracle Retail Invoice Matching, Oracle Retail Merchandising System, Oracle Retail Service Backbone and 3 more.

## How do I fix CVE-2019-17091?

Upgrade org.glassfish:jakarta.faces to 2.3.10 or later.

## Is CVE-2019-17091 being exploited?

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

## Other vulnerabilities in Oracle Application Testing Suite

- [CVE-2026-46581](https://insights.sbomify.com/CVE-2026-46581/): Server-side request forgery in Eclipse Mojarra (high 7.5)
- [CVE-2018-14371](https://insights.sbomify.com/CVE-2018-14371/): Path Traversal in Eclipse Mojarra (high 7.5)
- [CVE-2020-6950](https://insights.sbomify.com/CVE-2020-6950/): Directory traversal in Eclipse Mojarra (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-17091 and fix it if it is affected.

What it is: CVE-2019-17091 is a medium-severity cross-site scripting vulnerability in Oracle Application Testing Suite, published on 2 Oct 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-17091 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.glassfish:jakarta.faces (Maven): affected all versions; fixed in 2.3.10
- org.glassfish:jakarta.faces (Maven): affected all versions; fixed in 2.3.10
- org.glassfish:javax.faces (Maven): affected all versions; fixed in 2.2.20
- org.glassfish:javax.faces (Maven): affected all versions; fixed in 2.2.20

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

## Sources

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

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