# CVE-2001-0829: Apache Tomcat allows webmasters to insert xss into error messages

> A malicious webmaster can inject JavaScript into Tomcat error messages via JSP requests, potentially executing code in victim browsers.

- **Severity:** Medium 5.1 (`AV:N/AC:H/Au:N/C:P/I:P/A:P`)
- **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:** 22 Nov 2001
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-58hj-575g-5j25

## What is CVE-2001-0829?

CVE-2001-0829 is a medium-severity cross-site scripting vulnerability in Apache Tomcat, published on 22 Nov 2001. 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 cross-site scripting vulnerability in Apache Tomcat 3.2.1 allows a malicious webmaster to embed Javascript in a request for a .JSP file, which causes the Javascript to be inserted into an error message.

## Which versions are affected by CVE-2001-0829?

2 open source packages ship an affected version, including org.apache.tomcat:tomcat. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.tomcat:tomcat` | Maven | All versions to 3.2.1 | None |
| `org.apache.tomcat:tomcat` | Maven | All versions to 3.2.1 | None |

Products: Apache Tomcat.

## How do I fix CVE-2001-0829?

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

## Is CVE-2001-0829 being exploited?

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

## Other vulnerabilities in Apache Tomcat

- [CVE-2025-24813](https://insights.sbomify.com/CVE-2025-24813/): Apache Tomcat Path Equivalence (critical 10.0, exploited in the wild)
- [CVE-2016-8735](https://insights.sbomify.com/CVE-2016-8735/): Apache Tomcat Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2017-12617](https://insights.sbomify.com/CVE-2017-12617/): Apache Tomcat Remote Code Execution (high 8.1, exploited in the wild)
- [CVE-2017-12615](https://insights.sbomify.com/CVE-2017-12615/): Apache Tomcat on Windows Remote Code Execution (high 8.1, exploited in the wild)
- [CVE-2026-34486](https://insights.sbomify.com/CVE-2026-34486/): Apache Tomcat Missing Encryption of Sensitive Data (high 7.5, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2001-0829 and fix it if it is affected.

What it is: CVE-2001-0829 is a medium-severity cross-site scripting vulnerability in Apache Tomcat, published on 22 Nov 2001. 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-2001-0829 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.tomcat:tomcat (Maven): affected all versions up to 3.2.1; no fix listed
- org.apache.tomcat:tomcat (Maven): affected all versions up to 3.2.1; 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-2001-0829/ (Markdown: https://insights.sbomify.com/CVE-2001-0829/index.md)
```

## Sources

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

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