CVE-2022-25762: Response mix-up with WebSocket concurrent send and close
Noroxi assessment
Priority: Monitor (action score 37/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 8.4% (FIRST EPSS); higher than 95% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: tomcat9 (Debian:12) 9.0.22-1; org.apache.tomcat:tomcat (Maven) 8.5.75, 9.0.20; apache-commons-collections (Red Hat:enterprise_linux:8::appstream) 0:3.2.2-10.module+el8.1.0+3366+6dfb954c.
Low priority for now. Upgrade to tomcat9 (Debian:12) 9.0.22-1; org.apache.tomcat:tomcat (Maven) 8.5.75, 9.0.20; apache-commons-collections (Red Hat:enterprise_linux:8::appstream) 0:3.2.2-10.module+el8.1.0+3366+6dfb954c or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- May 13, 2022
- Updated
- Oct 8, 2026
- EPSS
- 8.4% · 95th percentile
- CWE
- CWE-404
Report tools
Action score
37
Low priority for now.
- CVSS
- 34 / 40 · 8.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 3 / 30 · 8.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| apache | tomcat | cpe:2.3:a:apache:tomcat |
| oracle | agile product lifecycle management | cpe:2.3:a:oracle:agile_product_lifecycle_management |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.
Apache Software Foundation Apache Tomcat
- Apache Tomcat 9 9.0.0.M1 to 9.0.20, Apache Tomcat 8.5 8.5.0 to 8.5.75affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- apache tomcat8.5.0 and later · before 8.5.76
- apache tomcat9.0.0 and later · before 9.0.21
- oracle agile product lifecycle management9.3.6
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | tomcat9 | before 9.0.22-1 | 9.0.22-1 |
| Maven | org.apache.tomcat:tomcat | from 8.5.0 · before 8.5.75 | 8.5.75 |
| Maven | org.apache.tomcat:tomcat | from 9.0.0M1 · before 9.0.20 | 9.0.20 |
| Red Hat:enterprise_linux:8::appstream | apache-commons-collections | before 0:3.2.2-10.module+el8.1.0+3366+6dfb954c | 0:3.2.2-10.module+el8.1.0+3366+6dfb954c |
| Red Hat:enterprise_linux:8::appstream | apache-commons-lang | before 0:2.6-21.module+el8.1.0+3366+6dfb954c | 0:2.6-21.module+el8.1.0+3366+6dfb954c |
| Red Hat:enterprise_linux:8::appstream | apache-commons-net | before 0:3.6-3.module+el8.3.0+6805+72837426 | 0:3.6-3.module+el8.3.0+6805+72837426 |
| Red Hat:enterprise_linux:8::appstream | bea-stax | before 0:1.2.0-16.module+el8.1.0+3366+6dfb954c | 0:1.2.0-16.module+el8.1.0+3366+6dfb954c |
| Red Hat:enterprise_linux:8::appstream | bea-stax-api | before 0:1.2.0-16.module+el8.1.0+3366+6dfb954c | 0:1.2.0-16.module+el8.1.0+3366+6dfb954c |
| Red Hat:enterprise_linux:8::appstream | glassfish-fastinfoset | before 0:1.2.13-9.module+el8.1.0+3366+6dfb954c | 0:1.2.13-9.module+el8.1.0+3366+6dfb954c |
| Red Hat:enterprise_linux:8::appstream | glassfish-jaxb | before 0:2.2.11-11.module+el8.1.0+3366+6dfb954c | 0:2.2.11-11.module+el8.1.0+3366+6dfb954c |
| Red Hat:enterprise_linux:8::appstream | glassfish-jaxb-api | before 0:2.2.12-8.module+el8.1.0+3366+6dfb954c | 0:2.2.12-8.module+el8.1.0+3366+6dfb954c |
| Red Hat:enterprise_linux:8::appstream | glassfish-jaxb-core | before 0:2.2.11-11.module+el8.1.0+3366+6dfb954c | 0:2.2.11-11.module+el8.1.0+3366+6dfb954c |
| Red Hat:enterprise_linux:8::appstream | glassfish-jaxb-runtime | before 0:2.2.11-11.module+el8.1.0+3366+6dfb954c | 0:2.2.11-11.module+el8.1.0+3366+6dfb954c |
| Red Hat:enterprise_linux:8::appstream | glassfish-jaxb-txw2 | before 0:2.2.11-11.module+el8.1.0+3366+6dfb954c | 0:2.2.11-11.module+el8.1.0+3366+6dfb954c |
| Red Hat:enterprise_linux:8::appstream | jackson-annotations | before 0:2.10.0-1.module+el8.2.0+5059+3eb3af25 | 0:2.10.0-1.module+el8.2.0+5059+3eb3af25 |
| Red Hat:enterprise_linux:8::appstream | jackson-core | before 0:2.10.0-1.module+el8.2.0+5059+3eb3af25 | 0:2.10.0-1.module+el8.2.0+5059+3eb3af25 |
| Red Hat:enterprise_linux:8::appstream | jackson-databind | before 0:2.10.0-1.module+el8.2.0+5059+3eb3af25 | 0:2.10.0-1.module+el8.2.0+5059+3eb3af25 |
| Red Hat:enterprise_linux:8::appstream | jackson-jaxrs-json-provider | before 0:2.9.9-1.module+el8.1.0+3832+9784644d | 0:2.9.9-1.module+el8.1.0+3832+9784644d |
| Red Hat:enterprise_linux:8::appstream | jackson-jaxrs-providers | before 0:2.9.9-1.module+el8.1.0+3832+9784644d | 0:2.9.9-1.module+el8.1.0+3832+9784644d |
| Red Hat:enterprise_linux:8::appstream | jackson-module-jaxb-annotations | before 0:2.7.6-4.module+el8.1.0+3366+6dfb954c | 0:2.7.6-4.module+el8.1.0+3366+6dfb954c |
| Red Hat:enterprise_linux:8::appstream | jakarta-commons-httpclient | before 1:3.1-28.module+el8.1.0+3366+6dfb954c | 1:3.1-28.module+el8.1.0+3366+6dfb954c |
| Red Hat:enterprise_linux:8::appstream | javassist | before 0:3.18.1-8.module+el8.1.0+3366+6dfb954c | 0:3.18.1-8.module+el8.1.0+3366+6dfb954c |
| Red Hat:enterprise_linux:8::appstream | javassist-javadoc | before 0:3.18.1-8.module+el8.1.0+3366+6dfb954c | 0:3.18.1-8.module+el8.1.0+3366+6dfb954c |
| Red Hat:enterprise_linux:8::appstream | jss | before 0:4.7.3-1.module+el8.3.0+8058+d5cd4219 | 0:4.7.3-1.module+el8.3.0+8058+d5cd4219 |
+79
Same product
apache: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-24813Apache Tomcat: Potential RCE and/or information disclosure and/or information corruption with partial PUTKEV99Now
- CVE-2016-8735Remote code execution is possible with Apache Tomcat before 6.0.48, 7.x before 7.0.73, 8.x before 8.0.39, 8.5.x before 8.5.7, and 9.x…KEV96Now
- CVE-2017-12617When running Apache Tomcat versions 9.0.0.M1 to 9.0.0, 8.5.0 to 8.5.22, 8.0.0.RC1 to 8.0.46 and 7.0.0 to 7.0.81 with HTTP PUTs enabled (e.g.KEV92Now
Published before and after this one in the same product
- ← EarlierCVE-2022-23181Jan 27, 2022 · Local privilege escalation with FileStore28Monitor
- ← EarlierCVE-2022-29885May 12, 2022 · EncryptInterceptor does not provide complete protection on insecure networks52Plan
- Later →CVE-2022-34305Jun 23, 2022 · XSS in examples web application26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:tomcat9 | 9.0.22-1 · Debian:12 | Package registry (OSV) |
| Maven:org.apache.tomcat:tomcat | 8.5.75 | Package registry (OSV) |
| Maven:org.apache.tomcat:tomcat | 9.0.20 | Package registry (OSV) |
| red hat:apache-commons-collections | 0:3.2.2-10.module+el8.1.0+3366+6dfb954c · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:apache-commons-lang | 0:2.6-21.module+el8.1.0+3366+6dfb954c · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:apache-commons-net | 0:3.6-3.module+el8.3.0+6805+72837426 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:bea-stax | 0:1.2.0-16.module+el8.1.0+3366+6dfb954c · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:bea-stax-api | 0:1.2.0-16.module+el8.1.0+3366+6dfb954c · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:glassfish-fastinfoset | 0:1.2.13-9.module+el8.1.0+3366+6dfb954c · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:glassfish-jaxb | 0:2.2.11-11.module+el8.1.0+3366+6dfb954c · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:glassfish-jaxb-api | 0:2.2.12-8.module+el8.1.0+3366+6dfb954c · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:glassfish-jaxb-core | 0:2.2.11-11.module+el8.1.0+3366+6dfb954c · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:glassfish-jaxb-runtime | 0:2.2.11-11.module+el8.1.0+3366+6dfb954c · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:glassfish-jaxb-txw2 | 0:2.2.11-11.module+el8.1.0+3366+6dfb954c · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:jackson-annotations | 0:2.10.0-1.module+el8.2.0+5059+3eb3af25 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| rocky linux:apache-commons-collections | 0:3.2.2-10.module+el8.3.0+53+ea062990 · Rocky Linux:8 | Package registry (OSV) |
| rocky linux:apache-commons-lang | 0:2.6-21.module+el8.3.0+53+ea062990 · Rocky Linux:8 | Package registry (OSV) |
| rocky linux:apache-commons-net | 0:3.6-3.module+el8.3.0+53+ea062990 · Rocky Linux:8 | Package registry (OSV) |
| rocky linux:bea-stax | 0:1.2.0-16.module+el8.3.0+53+ea062990 · Rocky Linux:8 | Package registry (OSV) |
| rocky linux:glassfish-fastinfoset | 0:1.2.13-9.module+el8.3.0+53+ea062990 · Rocky Linux:8 | Package registry (OSV) |
| rocky linux:glassfish-jaxb | 0:2.2.11-11.module+el8.3.0+53+ea062990 · Rocky Linux:8 | Package registry (OSV) |
| rocky linux:glassfish-jaxb-api | 0:2.2.12-8.module+el8.3.0+53+ea062990 · Rocky Linux:8 | Package registry (OSV) |
| rocky linux:jackson-annotations | 0:2.10.0-1.module+el8.3.0+53+ea062990 · Rocky Linux:8 | Package registry (OSV) |
| rocky linux:jackson-core | 0:2.10.0-1.module+el8.3.0+53+ea062990 · Rocky Linux:8 | Package registry (OSV) |
| rocky linux:jackson-databind | 0:2.10.0-1.module+el8.3.0+53+ea062990 · Rocky Linux:8 | Package registry (OSV) |
| rocky linux:jackson-jaxrs-providers | 0:2.9.9-1.module+el8.3.0+53+ea062990 · Rocky Linux:8 | Package registry (OSV) |
| rocky linux:jackson-module-jaxb-annotations | 0:2.7.6-4.module+el8.3.0+53+ea062990 · Rocky Linux:8 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- low · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- Low
- Availability impact
- Low
Weakness class (CWE)
CWE-404 · Improper Resource Shutdown or ReleaseCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
Change log (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.