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.
The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources.
| 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 | * |
Limited resources include memory, file system storage, database connection pool entries, and CPU. If an attacker can trigger the allocation of these limited resources, but the number or size of the resources is not controlled, then the attacker could cause a denial of service that consumes all available resources. This would prevent valid users from accessing the product, and it could potentially have an impact on the surrounding environment. For example, a memory exhaustion attack against an application could slow down the application as well as its host operating system. There are at least three distinct scenarios which can commonly lead to resource exhaustion:
Resource exhaustion problems are often result due to an incorrect implementation of the following situations:
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.