CVE-2022-34305

In Apache Tomcat 10.1.0-M1 to 10.1.0-M16, 10.0.0-M1 to 10.0.22, 9.0.30 to 9.0.64 and 8.5.50 to 8.5.81 the Form authentication example in the examples web application displayed user provided data without filtering, exposing a XSS vulnerability.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2022-34305 has a CVSS score of 6.1 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (10.1.0-M17, 10.0.22, 9.0.65, 8.5.82); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2022-34305? CVE-2022-34305 is a medium-severity cross-site scripting (XSS) vulnerability in org.apache.tomcat:tomcat (maven), affecting versions >= 10.1.0-M1, <= 10.1.0-M16. It is fixed in 10.1.0-M17, 10.0.22, 9.0.65, 8.5.82. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2022-34305? CVE-2022-34305 has a CVSS score of 6.1 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.apache.tomcat:tomcat are affected by CVE-2022-34305? org.apache.tomcat:tomcat (maven) versions >= 10.1.0-M1, <= 10.1.0-M16 is affected.
4. Is there a fix for CVE-2022-34305? Yes. CVE-2022-34305 is fixed in 10.1.0-M17, 10.0.22, 9.0.65, 8.5.82. Upgrade to this version or later.
5. Is CVE-2022-34305 exploitable, and should I be worried? Whether CVE-2022-34305 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-34305 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-34305?
   • Upgrade org.apache.tomcat:tomcat to 10.1.0-M17 or later
   • Upgrade org.apache.tomcat:tomcat to 10.0.22 or later
   • Upgrade org.apache.tomcat:tomcat to 9.0.65 or later
   • Upgrade org.apache.tomcat:tomcat to 8.5.82 or later