dbcve.org
TomcatWeb server / proxy · Apache

CVE-2022-23181

HIGH · 7.0 CVSS v3.1 Published 2022-01-27
Fix available
A fix is available. Upgrade to after 10.0.14 or later.
See remediation →
72/100
Remediation priority · Elevated
Zero-click Patch available

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
The fix for bug CVE-2020-9484 introduced a time of check, time of use vulnerability into Apache Tomcat 10.1.0-M1 to 10.1.0-M8, 10.0.0-M5 to 10.0.14, 9.0.35 to 9.0.56 and 8.5.55 to 8.5.73 that allowed a local attacker to perform actions with the privileges of the user that the Tomcat process is using. This issue is only exploitable when Tomcat is configured to persist sessions using the FileStore.

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

A detailed technical summary for this CVE is being prepared.

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.55, <= 8.5.73>= 9.0.35, <= 9.0.56>= 10.0.1, <= 10.0.14= 10.0.0= 10.1.0
Debian LinuxOperating system
Affected:= 10.0= 11.0
Agile Engineering Data ManagementApplication
Affected:= 6.2.1.0
Communications Cloud Native Core PolicyApplication
Affected:= 1.15.0
Financial Services Crime And Compliance Management StudioApplication
Affected:= 8.0.8.2.0= 8.0.8.3.0
Managed File TransferApplication
Affected:= 12.2.1.3.0= 12.2.1.4.0
Mysql Enterprise MonitorDatabase / datastore
Affected:<= 8.0.29

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
Local
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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.14
Vendor patch www.oracle.com →
Recommended fix High confidence

Tomcat 8.5.74+, 9.0.57+, 10.0.15+, or 10.1.0-M9+ (depending on your current major version); or patched Oracle product versions from CPU April 2022

  1. 1. Identify all Tomcat instances in your environment and verify their exact versions using bin/version.sh or checking the server banner.
  2. 2. Identify whether FileStore session persistence is configured (look for <Manager pathname="..." /> in context.xml or server.xml files).
  3. 3. If using FileStore and upgrade is not immediately feasible, consider alternative session persistence mechanisms (e.g., Redis, JDBCStore) as a temporary mitigation.
  4. 4. For each affected Tomcat instance, download the corresponding fixed release: 8.5.74 or later for 8.5.x, 9.0.57 or later for 9.0.x, 10.0.15 or later for 10.0.x, 10.1.0-M9 or later for 10.1.x.
  5. 5. Test the upgrade in a non-production environment first, verifying application compatibility.
  6. 6. Schedule maintenance window and back up current Tomcat configuration and deployed applications.
  7. 7. Stop the running Tomcat instance.
  8. 8. Replace the Tomcat installation directory with the new version, preserving your configuration files and deployed applications.
Caveat Minor Tomcat version upgrades typically have low risk, but always test application compatibility in staging first as session handling behavior may have subtle changes

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

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-23181 — 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-23181 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