# CVE-2021-42575: Policies not properly enforced in OWASP Java HTML Sanitizer

> The OWASP Java HTML Sanitizer fails to enforce policies for SELECT, STYLE, and OPTION elements, allowing attackers to inject malicious scripts.

- **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:** 18 Oct 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-3w73-fmf3-hg5c

## What is CVE-2021-42575?

CVE-2021-42575 is a critical cross-site scripting vulnerability in Oracle Primavera Unifier, published on 18 Oct 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The OWASP Java HTML Sanitizer before 20211018.1 does not properly enforce policies associated with the SELECT, STYLE, and OPTION elements.

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

2 open source packages ship an affected version, including com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer. It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer` | Maven | All versions | 20211018.1 |
| `com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer` | Maven | All versions | 20211018.1 |

Products: Oracle Middleware Common Libraries and Tools, Oracle Primavera Unifier, Owasp Java Html Sanitizer.

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

Upgrade com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer to 20211018.1 or later.

## Is CVE-2021-42575 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-42575 is a critical cross-site scripting vulnerability in Oracle Primavera Unifier, published on 18 Oct 2021. 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-2021-42575 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer (Maven): affected all versions; fixed in 20211018.1
- com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer (Maven): affected all versions; fixed in 20211018.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-2021-42575/ (Markdown: https://insights.sbomify.com/CVE-2021-42575/index.md)
```

## Sources

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

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