FlawAtlas
Search the atlas
CVE-2022-45143 High

Apache Tomcat: JsonErrorReportValve escaping

The JsonErrorReportValve in Apache Tomcat 8.5.83, 9.0.40 to 9.0.68 and 10.1.0 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.

Exploit probability 2.5%
Published March 6, 2024
Required by Not available
Last source change March 20, 2026

02 / AFFECTED SOFTWARE

Affected packages

Unknown Unknown

19 explicit affected versions

Bitnami tomcat
Maven org.apache.tomcat.embed:tomcat-embed-core

25 explicit affected versions

Maven org.apache.tomcat:tomcat-catalina

2 explicit affected versions

Maven org.apache.tomcat:tomcat-util

23 explicit affected versions

03 / CONNECTIONS

Connected vulnerabilities

04 / EVIDENCE

Source records

Open Source Vulnerabilities BIT-tomcat-2022-45143

The JsonErrorReportValve in Apache Tomcat 8.5.83, 9.0.40 to 9.0.68 and 10.1.0 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.

View original source
Open Source Vulnerabilities GHSA-rq2w-37h9-vg94

The `JsonErrorReportValve` in Apache Tomcat 8.5.83, 9.0.40 to 9.0.68 and 10.1.0-M1 to 10.1.1 does 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.

View original source
Open Source Vulnerabilities CVE-2022-45143

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.

View original source

05 / REFERENCES

Further evidence