# CVE-2019-0221: Cross-site scripting in Apache Tomcat > Cross-site scripting vulnerability in Apache Tomcat SSI printenv command allows attackers to execute arbitrary scripts if SSI is enabled. - **Severity:** Medium 6.1 (`CVSS:3.0/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:** 28 May 2019 - **Updated:** 4 Aug 2024 - **Also known as:** CLSA-2022-1670606563, DEBIAN-CVE-2019-0221, DLA-1810-1, GHSA-jjpq-gp5q-8q6w, UBUNTU-CVE-2019-0221 ## What is CVE-2019-0221? CVE-2019-0221 is a medium-severity cross-site scripting vulnerability in Apache Tomcat, published on 28 May 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 The SSI printenv command in Apache Tomcat 9.0.0.M1 to 9.0.0.17, 8.5.0 to 8.5.39 and 7.0.0 to 7.0.93 echoes user provided data without escaping and is, therefore, vulnerable to XSS. SSI is disabled by default. The printenv command is intended for debugging and is unlikely to be present in a production website. Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2019-0221? 18 open source packages ship an affected version, including org.apache.tomcat.embed:tomcat-embed-core, org.apache.tomcat:tomcat and org.apache.tomcat:tomcat-catalina. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 7.0.0 | 7.0.94 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 7.0.0 | 7.0.94 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 8.5.0 | 8.5.40 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 8.5.0 | 8.5.40 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 9.0.0 | 9.0.17 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 9.0.0 | 9.0.17 | | `org.apache.tomcat:tomcat` | Maven | From 7.0.0 | 7.0.94 | | `org.apache.tomcat:tomcat` | Maven | From 7.0.0 | 7.0.94 | | `org.apache.tomcat:tomcat` | Maven | From 8.5.0 | 8.5.40 | | `org.apache.tomcat:tomcat` | Maven | From 8.5.0 | 8.5.40 | | `org.apache.tomcat:tomcat` | Maven | From 9.0.0 | 9.0.17 | | `org.apache.tomcat:tomcat` | Maven | From 9.0.0 | 9.0.17 | | `org.apache.tomcat:tomcat-catalina` | Maven | From 7.0.0 | 7.0.94 | | `org.apache.tomcat:tomcat-catalina` | Maven | From 7.0.0 | 7.0.94 | | `org.apache.tomcat:tomcat-catalina` | Maven | From 8.5.0 | 8.5.40 | | `org.apache.tomcat:tomcat-catalina` | Maven | From 8.5.0 | 8.5.40 | | `org.apache.tomcat:tomcat-catalina` | Maven | From 9.0.0 | 9.0.17 | | `org.apache.tomcat:tomcat-catalina` | Maven | From 9.0.0 | 9.0.17 | Products: Apache Tomcat. ## How do I fix CVE-2019-0221? Upgrade org.apache.tomcat.embed:tomcat-embed-core to a fixed version for your release line: 7.0.94, 8.5.40 or 9.0.17. ## Is CVE-2019-0221 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-0221 exists. Public exploit code: - Apache Tomcat 9.0.0.M1 - Cross-Site Scripting (XSS) (exploitdb) - Apache Tomcat - Cross-Site Scripting (nuclei): http/cves/2019/CVE-2019-0221.yaml ## 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-2019-0221 and fix it if it is affected. What it is: CVE-2019-0221 is a medium-severity cross-site scripting vulnerability in Apache Tomcat, published on 28 May 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-0221 exists. Affected packages and fixed versions: - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 7.0.0; fixed in 7.0.94 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 7.0.0; fixed in 7.0.94 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 8.5.0; fixed in 8.5.40 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 8.5.0; fixed in 8.5.40 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 9.0.0; fixed in 9.0.17 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 9.0.0; fixed in 9.0.17 - org.apache.tomcat:tomcat (Maven): affected from 7.0.0; fixed in 7.0.94 - org.apache.tomcat:tomcat (Maven): affected from 7.0.0; fixed in 7.0.94 - org.apache.tomcat:tomcat (Maven): affected from 8.5.0; fixed in 8.5.40 - org.apache.tomcat:tomcat (Maven): affected from 8.5.0; fixed in 8.5.40 - org.apache.tomcat:tomcat (Maven): affected from 9.0.0; fixed in 9.0.17 - org.apache.tomcat:tomcat (Maven): affected from 9.0.0; fixed in 9.0.17 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-0221/ (Markdown: https://insights.sbomify.com/CVE-2019-0221/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-0221 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-0221 - OSV: https://osv.dev/vulnerability/CVE-2019-0221 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-0221/ Summaries are generated and may contain mistakes; the official description above is the record.