Apache Tomcat EncryptInterceptor error leads to Uncontrolled Resource Consumption
Published 13 May 2022 · Updated 11 Mar 2024
Is your project on an affected org.apache.tomcat:tomcat?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=10.1.0-M1 <10.1.0-M15
- Fixed in
- 10.1.0-M15
mvn versions:use-dep-version -Dincludes=org.apache.tomcat:tomcat -DdepVersion=10.1.0-M15 -DforceVersion=true- Affected
- >=10.0.0-M1 <10.0.21
- Fixed in
- 10.0.21
mvn versions:use-dep-version -Dincludes=org.apache.tomcat:tomcat -DdepVersion=10.0.21 -DforceVersion=true- Affected
- >=9.0.13 <9.0.63
- Fixed in
- 9.0.63
mvn versions:use-dep-version -Dincludes=org.apache.tomcat:tomcat -DdepVersion=9.0.63 -DforceVersion=true- Affected
- >=8.5.38 <8.5.79
- Fixed in
- 8.5.79
mvn versions:use-dep-version -Dincludes=org.apache.tomcat:tomcat -DdepVersion=8.5.79 -DforceVersion=trueDetails
The documentation of Apache Tomcat 10.1.0-M1 to 10.1.0-M14, 10.0.0-M1 to 10.0.20, 9.0.13 to 9.0.62 and 8.5.38 to 8.5.78 for the EncryptInterceptor incorrectly stated it enabled Tomcat clustering to run over an untrusted network. This was not correct. While the EncryptInterceptor does provide confidentiality and integrity protection, it does not protect against all risks associated with running over any untrusted network, particularly DoS risks.
Is GHSA-r84p-88g2-2vx2 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.apache.tomcat:tomcat, and gives you the command that fixes it.
More advisories for org.apache.tomcat:tomcat
- CriticalCVE-2026-65905Apache Tomcat's DIGEST authenticator has an Authentication Bypass by Capture-replay vulnerability · 26 Aug 2026
- CriticalCVE-2026-65182Apache Tomcat has an Improper Access Control, Incorrect Authorization vulnerability · 26 Aug 2026
- CriticalCVE-2026-68525Apache Tomcat's FORM authentication process has an Incorrect Authorization vulnerability · 26 Aug 2026
- CriticalCVE-2026-55276Apache Tomcat has an Always-Incorrect Control Flow Implementation vulnerability · 29 Jun 2026
- HighCVE-2026-55957Apache Tomcat has a Missing Critical Step in Authentication vulnerability · 29 Jun 2026
- HighCVE-2026-53404Apache Tomcat's rewrite valve has an Always-Incorrect Control Flow Implementation vulnerability · 29 Jun 2026
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2022-29885
- Linkgithub.com/apache/tomcat/commit/0fa7721f11d565a2cd2e44366c388ad6a3e6357d
- Linkgithub.com/apache/tomcat/commit/36826ea638457d7e17876a70f89cb435b6db0d91
- Linkgithub.com/apache/tomcat/commit/b679bc627f5a4ea6510af95adfb7476b07eba890
- Linkgithub.com/apache/tomcat/commit/eaafd28296c54d983e28a47953c1f5cb2c334f48
- Packagegithub.com/apache/tomcat
- Linklists.apache.org/thread/2b4qmhbcyqvc7dyfpjyx54c03x65vhcv
- Linklists.debian.org/debian-lts-announce/2022/10/msg00029.html
- Linksecurity.netapp.com/advisory/ntap-20220629-0002
- Linkwww.debian.org/security/2022/dsa-5265
- Linkwww.oracle.com/security-alerts/cpujul2022.html
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.