# CVE-2021-20293: Cross-Site Scripting

> Reflected XSS in RESTEasy allows attackers to execute scripts via URL encoding flaws, compromising data confidentiality and integrity.

- **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:** No
- **Published:** 10 Jun 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-5h26-c766-g93v

## What is CVE-2021-20293?

CVE-2021-20293 is a medium-severity cross-site scripting vulnerability in Netapp Oncommand Insight, published on 10 Jun 2021. 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

A reflected Cross-Site Scripting (XSS) flaw was found in RESTEasy in all versions of RESTEasy up to 4.6.0.Final, where it did not properly handle URL encoding when calling @javax.ws.rs.PathParam without any @Produces MediaType. This flaw allows an attacker to launch a reflected XSS attack. The highest threat from this vulnerability is to data confidentiality and integrity.

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

## Which versions are affected by CVE-2021-20293?

4 open source packages ship an affected version, including org.jboss.resteasy:resteasy-bom and org.jboss.resteasy:resteasy-core. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jboss.resteasy:resteasy-bom` | Maven | All versions to 4.6.0.Final | None |
| `org.jboss.resteasy:resteasy-bom` | Maven | All versions to 4.6.0.Final | None |
| `org.jboss.resteasy:resteasy-core` | Maven | All versions to 4.6.0.Final | None |
| `org.jboss.resteasy:resteasy-core` | Maven | All versions to 4.6.0.Final | None |

Products: Netapp Oncommand Insight, Redhat Resteasy.

## How do I fix CVE-2021-20293?

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

## Is CVE-2021-20293 being exploited?

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

## Other vulnerabilities in Netapp Oncommand Insight

- [CVE-2017-5600](https://insights.sbomify.com/CVE-2017-5600/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2018-1258](https://insights.sbomify.com/CVE-2018-1258/): Spring Framework when used in combination with any versions of Spring Security contains an authorization bypass (high 8.8)
- [CVE-2020-5421](https://insights.sbomify.com/CVE-2020-5421/): RFD Protection Bypass via jsessionid (high 8.7)
- [CVE-2022-38733](https://insights.sbomify.com/CVE-2022-38733/): Auth bypass in OnCommand Insight (high 8.6)
- [CVE-2023-22102](https://insights.sbomify.com/CVE-2023-22102/): MySQL Connectors takeover vulnerability (high 8.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-20293 and fix it if it is affected.

What it is: CVE-2021-20293 is a medium-severity cross-site scripting vulnerability in Netapp Oncommand Insight, published on 10 Jun 2021. 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-2021-20293 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jboss.resteasy:resteasy-bom (Maven): affected all versions up to 4.6.0.Final; no fix listed
- org.jboss.resteasy:resteasy-bom (Maven): affected all versions up to 4.6.0.Final; no fix listed
- org.jboss.resteasy:resteasy-core (Maven): affected all versions up to 4.6.0.Final; no fix listed
- org.jboss.resteasy:resteasy-core (Maven): affected all versions up to 4.6.0.Final; 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-2021-20293/ (Markdown: https://insights.sbomify.com/CVE-2021-20293/index.md)
```

## Sources

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

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