dbcve.org
TomcatWeb server / proxy · Apache

CVE-2022-34305

MEDIUM · 6.1 CVSS v3.1 Published 2022-06-23
Fix available
A fix is available. Upgrade to after 10.0.22 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Tomcat contains an XSS vulnerability in the examples web application's Form authentication feature. The vulnerability occurs because user-provided input is displayed without proper filtering or encoding, allowing attackers to inject malicious scripts that execute in other users' browsers.

MitigationRemove the examples web application from production Tomcat deployments, or apply the vendor patch (upgraded Tomcat versions: 10.1.0-M17+, 10.0.23+, 9.0.65+, 8.5.82+). The examples application should never be deployed in production environments.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TomcatWeb server / proxy
Affected:>= 8.5.50, <= 8.5.81>= 9.0.30, <= 9.0.64>= 10.0.0, <= 10.0.22= 10.1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Tomcat version
    Check the server info by reading the banner file (typically in $CATALINA_HOME/README RELEASE-NOTES or by calling the JSP servlet info). In a running instance, access the default 404 page or check the server.xml for the version number.
    Affected if The installed version falls within: 8.5.50-8.5.81, 9.0.30-9.0.64, 10.0.0-10.0.22, or is exactly 10.1.0
  2. Locate the examples web application
    Inspect the webapps directory (typically $CATALINA_HOME/webapps/) for the presence of the 'examples' folder or examples.war file.
    Affected if The examples directory or examples.war file exists in the webapps folder
  3. Verify the examples application is deployed and accessible
    Attempt to access the examples application through HTTP request to confirm it is running. Common paths include /examples/jsp/security/protected/ or check if the application is in a 'deployed' or 'running' state in the manager application.
    Affected if The examples application responds to requests and is not explicitly undeployed or removed

A user is affected only if their Tomcat version is within the affected ranges AND the examples web application is present and accessible in their deployment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 10.0.22
Interim mitigation

Remove the examples web application from production Tomcat deployments, or apply the vendor patch (upgraded Tomcat versions: 10.1.0-M17+, 10.0.23+, 9.0.65+, 8.5.82+). The examples application should never be deployed in production environments.

Recommended fix High confidence

8.5.96 (8.5.x) / 9.0.97 (9.0.x) / 10.0.27 (10.0.x) / 10.1.34 (10.1.x)

  1. Identify the currently installed Tomcat version using the bin/version.sh script or check the RELEASE-NOTES file
  2. Determine which Tomcat branch your version belongs to (8.5.x, 9.0.x, 10.0.x, or 10.1.x)
  3. Download the appropriate fixed Tomcat version from the Apache Tomcat downloads page (tomcat.apache.org)
  4. Stop the Tomcat service running the affected instance
  5. Create a backup of the existing Tomcat installation directory
  6. Extract the new Tomcat version to a temporary location
  7. Copy the conf directory from the backup to the new installation, preserving custom configurations
  8. Deploy any custom web applications to the new installation's webapps directory
Caveat Minimal risk; the vulnerability is in the examples web application which should not be present in production. Ensure custom configurations are preserved during upgrade.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tomcat Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-34305 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-34305 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data