# CVE-2022-45143: Apache Tomcat: JsonErrorReportValve escaping > Attackers can inject malicious scripts into JSON error responses via unescaped user data in Apache Tomcat's JsonErrorReportValve, potentially leading to XSS. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 3 Jan 2023 - **Updated:** 3 Aug 2024 - **Also known as:** BIT-tomcat-2022-45143, CLEANSTART-2026-NO70924, DEBIAN-CVE-2022-45143, GHSA-rq2w-37h9-vg94, ROOT-APP-MAVEN-CVE-2022-45143, SUSE-SU-2023:1853-1, UBUNTU-CVE-2022-45143, openSUSE-SU-2024:12847-1 ## What is CVE-2022-45143? CVE-2022-45143 is a high-severity cross-site scripting vulnerability in Apache Tomcat, published on 3 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description The JsonErrorReportValve in Apache Tomcat 8.5.83, 9.0.40 to 9.0.68 and 10.1.0-M1 to 10.1.1 did not escape the type, message or description values. In some circumstances these are constructed from user provided data and it was therefore possible for users to supply values that invalidated or manipulated the JSON output. Weakness: CWE-116 (Improper Encoding or Escaping of Output) ## Which versions are affected by CVE-2022-45143? 13 open source packages ship an affected version, including org.apache.tomcat.embed:tomcat-embed-core, 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 10.1.0 | 10.1.2 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 10.1.0 | 10.1.2 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 8.5.83 | 8.5.84 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 8.5.83 | 8.5.84 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 9.0.40 | 9.0.69 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 9.0.40 | 9.0.69 | | `tomcat` | Bitnami | From 9.0.40 | 9.0.69, 8.5.84, 10.1.2 | | `org.apache.tomcat:tomcat-catalina` | Maven | From 10.1.0 | 10.1.2 | | `org.apache.tomcat:tomcat-catalina` | Maven | From 10.1.0 | 10.1.2 | | `org.apache.tomcat:tomcat-util` | Maven | From 8.5.83 | 8.5.84 | | `org.apache.tomcat:tomcat-util` | Maven | From 8.5.83 | 8.5.84 | | `org.apache.tomcat:tomcat-util` | Maven | From 9.0.40 | 9.0.69 | | `org.apache.tomcat:tomcat-util` | Maven | From 9.0.40 | 9.0.69 | | `tomcat` | SUSE:Enterprise Storage 7 | All versions | 9.0.43-150200.38.1 | | `tomcat` | SUSE:Enterprise Storage 7.1 | All versions | 9.0.43-150200.38.1 | | `tomcat` | SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | All versions | 9.0.43-150200.38.1 | | `tomcat` | SUSE:Linux Enterprise High Performance Computing 15 SP3-ESPOS | All versions | 9.0.43-150200.38.1 | | `tomcat` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 9.0.43-150200.38.1 | | `tomcat` | SUSE:Linux Enterprise Module for Web and Scripting 15 SP4 | All versions | 9.0.43-150200.38.1 | | `tomcat` | SUSE:Linux Enterprise Server 15 SP2-LTSS | All versions | 9.0.43-150200.38.1 | | `tomcat` | SUSE:Linux Enterprise Server 15 SP3-LTSS | All versions | 9.0.43-150200.38.1 | | `tomcat` | SUSE:Linux Enterprise Server for SAP Applications 15 SP2 | All versions | 9.0.43-150200.38.1 | | `tomcat` | SUSE:Linux Enterprise Server for SAP Applications 15 SP3 | All versions | 9.0.43-150200.38.1 | | `tomcat` | SUSE:Manager Server 4.2 | All versions | 9.0.43-150200.38.1 | | `tomcat` | openSUSE:Leap 15.4 | All versions | 9.0.43-150200.38.1 | | `tomcat` | openSUSE:Tumbleweed | All versions | 9.0.43-16.1 | Products: Apache Tomcat. ## How do I fix CVE-2022-45143? Upgrade org.apache.tomcat.embed:tomcat-embed-core to a fixed version for your release line: 10.1.2, 8.5.84 or 9.0.69. ## Is CVE-2022-45143 being exploited? There is no known exploitation of CVE-2022-45143 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-2022-45143 and fix it if it is affected. What it is: CVE-2022-45143 is a high-severity cross-site scripting vulnerability in Apache Tomcat, published on 3 Jan 2023. 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-2022-45143 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 10.1.0; fixed in 10.1.2 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 10.1.0; fixed in 10.1.2 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 8.5.83; fixed in 8.5.84 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 8.5.83; fixed in 8.5.84 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 9.0.40; fixed in 9.0.69 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 9.0.40; fixed in 9.0.69 - tomcat (Bitnami): affected from 9.0.40; fixed in 9.0.69, 8.5.84, 10.1.2 - org.apache.tomcat:tomcat-catalina (Maven): affected from 10.1.0; fixed in 10.1.2 - org.apache.tomcat:tomcat-catalina (Maven): affected from 10.1.0; fixed in 10.1.2 - org.apache.tomcat:tomcat-util (Maven): affected from 8.5.83; fixed in 8.5.84 - org.apache.tomcat:tomcat-util (Maven): affected from 8.5.83; fixed in 8.5.84 - org.apache.tomcat:tomcat-util (Maven): affected from 9.0.40; fixed in 9.0.69 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-2022-45143/ (Markdown: https://insights.sbomify.com/CVE-2022-45143/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-45143 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-45143 - OSV: https://osv.dev/vulnerability/CVE-2022-45143 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-45143/ Summaries are generated and may contain mistakes; the official description above is the record.