In Eclipse Jetty 7.2.2 to 9.4.38, 10.0.0.alpha0 to 10.0.1, and 11.0.0.alpha0 to 11.0.1, CPU usage can reach 100% upon receiving a large invalid TLS frame.
The product does not properly control the allocation and maintenance of a limited resource.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Jetty | Eclipse | 7.2.2 (including) | 9.4.39 (excluding) |
| Jetty | Eclipse | 10.0.0 (including) | 10.0.2 (excluding) |
| Jetty | Eclipse | 11.0.0 (including) | 11.0.2 (excluding) |
| Red Hat AMQ 7.8.2 | RedHat | jetty-server | * |
| Red Hat AMQ 7.9.0 | RedHat | jetty-server | * |
| Red Hat AMQ Streams 1.6.4 | RedHat | jetty-server | * |
| Red Hat AMQ Streams 1.8.0 | RedHat | jetty-server | * |
| Red Hat Developer Tools | RedHat | rh-eclipse-jetty-0:9.4.40-1.1.el7_9 | * |
| Red Hat Fuse 7.9 | RedHat | jetty | * |
| Red Hat Integration Camel Quarkus 2 | RedHat | jetty | * |
| Red Hat OpenShift Container Platform 4.7 | RedHat | jenkins-0:2.277.3.1620393611-1.el8 | * |
| Red Hat OpenShift Container Platform 4.7 | RedHat | runc-0:1.0.0-95.rhaos4.8.gitcd80260.el7 | * |
| RHAF Camel-K 1.8 | RedHat | jetty | * |
| Equinox-bundles | Ubuntu | bionic | * |
| Equinox-bundles | Ubuntu | focal | * |
| Equinox-bundles | Ubuntu | groovy | * |
| Equinox-bundles | Ubuntu | hirsute | * |
| Equinox-bundles | Ubuntu | impish | * |
| Equinox-bundles | Ubuntu | kinetic | * |
| Equinox-bundles | Ubuntu | lunar | * |
| Equinox-bundles | Ubuntu | trusty | * |
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.