dbcve.org
TomcatWeb server / proxy · Apache

CVE-2022-25762

HIGH · 8.6 CVSS v3.1 Published 2022-05-13
Fix available
A fix is available. Upgrade to 8.5.76 / 9.0.21 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges 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
If a web application sends a WebSocket message concurrently with the WebSocket connection closing when running on Apache Tomcat 8.5.0 to 8.5.75 or Apache Tomcat 9.0.0.M1 to 9.0.20, it is possible that the application will continue to use the socket after it has been closed. The error handling triggered in this case could cause the a pooled object to be placed in the pool twice. This could result in subsequent connections using the same object concurrently which could result in data being returned to the wrong use and/or other errors.

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.0, < 8.5.76>= 9.0.0, < 9.0.21
Agile PlmApplication
Affected:= 9.3.6

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
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
Low

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

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 8.5.76 / 9.0.21 or later
Fixed in 8.5.769.0.21
Vendor patch www.oracle.com →
Recommended fix High confidence

Apache Tomcat 8.5.76+ or 9.0.21+ (or apply Oracle CPU July 2022 for Agile PLM)

  1. Identify the exact Apache Tomcat version currently installed (check CATALINA_HOME or catalina.jar manifest)
  2. If using Tomcat 8.5.x, upgrade to Tomcat 8.5.76 or later (8.5.76 is the first version containing the fix)
  3. If using Tomcat 9.0.x, upgrade to Tomcat 9.0.21 or later (9.0.21 is the first version containing the fix)
  4. For Agile PLM 9.3.6, apply the Oracle July 2022 Critical Patch Update per https://www.oracle.com/security-alerts/cpujul2022.html
  5. After upgrade, restart the Tomcat service
  6. Test WebSocket functionality to verify normal operation
Caveat Tomcat minor version upgrades typically have minimal breaking changes, but review Tomcat migration notes for any deprecation warnings between 8.5.0-8.5.75 or 9.0.0-9.0.20 and the target version

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

We can perform the upgrade in your staging environment and verify nothing breaks — 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-25762 — 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-25762 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