# CVE-2011-4457: OWASP HTML Sanitizer allows redirecting to an arbitrary URL when JavaScript is disabled

> Attackers can obtain sensitive information via crafted FORM elements in NOSCRIPT tags when JavaScript is disabled in the OWASP HTML Sanitizer library.

- **Severity:** Low 2.6 (`AV:N/AC:H/Au:N/C:P/I:N/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:** 17 Nov 2011
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-pcm9-fp55-563v

## What is CVE-2011-4457?

CVE-2011-4457 is a low-severity vulnerability in n/a, published on 17 Nov 2011. 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

OWASP HTML Sanitizer (aka owasp-java-html-sanitizer) before 88, when JavaScript is disabled, allows user-assisted remote attackers to obtain potentially sensitive information via a crafted FORM element within a NOSCRIPT element.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2011-4457?

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


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

Products: Owasp-Java-Html-Sanitizer Project Owasp-Java-Html-Sanitizer.

## How do I fix CVE-2011-4457?

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

## Is CVE-2011-4457 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-4457 and fix it if it is affected.

What it is: CVE-2011-4457 is a low-severity vulnerability in n/a, published on 17 Nov 2011. 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-2011-4457 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 88
- com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer (Maven): affected all versions; fixed in 88

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

## Sources

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

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