Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

CVE-2022-34305

MEDIUM

CVE-2022-34305 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in org.apache.tomcat:tomcat. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2022-34305 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

XSS in examples web application

Also known asBIT-tomcat-2022-34305GHSA-6j88-6whg-x687
Published
Jun 23, 2022
Updated
Jul 15, 2026
Affected
4 pkgs
Patched
4 / 4
Exploits
1 known

Real-World Exposure

4 pkgs affected
org.apache.tomcat:tomcatorg.apache.tomcat:tomcatorg.apache.tomcat:tomcatorg.apache.tomcat:tomcat

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.apache.tomcat:tomcat10.1.0-M1&&< 10.1.0-M1710.1.0-M17
Mavenorg.apache.tomcat:tomcat10.0.0-M1&&< 10.0.2210.0.22
Mavenorg.apache.tomcat:tomcat9.0.30&&< 9.0.659.0.65
Mavenorg.apache.tomcat:tomcat8.5.50&&< 8.5.828.5.82
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update org.apache.tomcat:tomcat to 10.1.0-M17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-34305 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2022-34305 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2022-34305. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2022-34305 in your dependencies?

O3 detects CVE-2022-34305 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.