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.
Weakness
The product does not properly control the allocation and maintenance of a limited resource.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Tomcat | Apache | 8.5.38 (including) | 8.5.78 (including) |
| Tomcat | Apache | 9.0.13 (including) | 9.0.62 (including) |
| Tomcat | Apache | 10.0.0 (including) | 10.0.20 (including) |
| Tomcat | Apache | 10.1.0-milestone1 (including) | 10.1.0-milestone1 (including) |
| Tomcat | Apache | 10.1.0-milestone10 (including) | 10.1.0-milestone10 (including) |
| Tomcat | Apache | 10.1.0-milestone11 (including) | 10.1.0-milestone11 (including) |
| Tomcat | Apache | 10.1.0-milestone12 (including) | 10.1.0-milestone12 (including) |
| Tomcat | Apache | 10.1.0-milestone13 (including) | 10.1.0-milestone13 (including) |
| Tomcat | Apache | 10.1.0-milestone14 (including) | 10.1.0-milestone14 (including) |
| Tomcat | Apache | 10.1.0-milestone2 (including) | 10.1.0-milestone2 (including) |
| Tomcat | Apache | 10.1.0-milestone3 (including) | 10.1.0-milestone3 (including) |
| Tomcat | Apache | 10.1.0-milestone4 (including) | 10.1.0-milestone4 (including) |
| Tomcat | Apache | 10.1.0-milestone5 (including) | 10.1.0-milestone5 (including) |
| Tomcat | Apache | 10.1.0-milestone6 (including) | 10.1.0-milestone6 (including) |
| Tomcat | Apache | 10.1.0-milestone7 (including) | 10.1.0-milestone7 (including) |
| Tomcat | Apache | 10.1.0-milestone8 (including) | 10.1.0-milestone8 (including) |
| Tomcat | Apache | 10.1.0-milestone9 (including) | 10.1.0-milestone9 (including) |
| Tomcat8 | Ubuntu | bionic | * |
| Tomcat8 | Ubuntu | esm-apps/bionic | * |
| Tomcat8 | Ubuntu | upstream | * |
| Tomcat9 | Ubuntu | bionic | * |
| Tomcat9 | Ubuntu | esm-apps/bionic | * |
| Tomcat9 | Ubuntu | esm-apps/focal | * |
| Tomcat9 | Ubuntu | esm-apps/jammy | * |
| Tomcat9 | Ubuntu | focal | * |
| Tomcat9 | Ubuntu | impish | * |
| Tomcat9 | Ubuntu | jammy | * |
| Tomcat9 | Ubuntu | upstream | * |
Potential Mitigations
Mitigation of resource exhaustion attacks requires that the target system either:
The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question.
The second solution is simply difficult to effectively institute – and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.
Related Attack Patterns
- https://cwe.mitre.org/data/definitions/147.html
- https://cwe.mitre.org/data/definitions/227.html
- https://cwe.mitre.org/data/definitions/492.html
References
- http://packetstormsecurity.com/files/171728/Apache-Tomcat-10.1-Denial-Of-Service.html
- https://lists.apache.org/thread/2b4qmhbcyqvc7dyfpjyx54c03x65vhcv
- https://lists.debian.org/debian-lts-announce/2022/10/msg00029.html
- https://security.netapp.com/advisory/ntap-20220629-0002/
- https://www.debian.org/security/2022/dsa-5265
- https://www.oracle.com/security-alerts/cpujul2022.html
- http://packetstormsecurity.com/files/171728/Apache-Tomcat-10.1-Denial-Of-Service.html
- https://lists.apache.org/thread/2b4qmhbcyqvc7dyfpjyx54c03x65vhcv
- https://lists.debian.org/debian-lts-announce/2022/10/msg00029.html
- https://security.netapp.com/advisory/ntap-20220629-0002/
- https://www.debian.org/security/2022/dsa-5265
- https://www.oracle.com/security-alerts/cpujul2022.html