Jetty is a Java based web server and servlet engine. An HTTP/2 SSL connection that is established and TCP congested will be leaked when it times out. An attacker can cause many connections to end up in this state, and the server may run out of file descriptors, eventually causing the server to stop accepting new connections from valid clients. The vulnerability is patched in 9.4.54, 10.0.20, 11.0.20, and 12.0.6.
Weakness
The product does not properly control the allocation and maintenance of a limited resource.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Jetty | Eclipse | 9.3.0 (including) | 9.4.54 (excluding) |
| Jetty | Eclipse | 10.0.0 (including) | 10.0.20 (excluding) |
| Jetty | Eclipse | 11.0.0 (including) | 11.0.20 (excluding) |
| Jetty | Eclipse | 12.0.0 (including) | 12.0.6 (excluding) |
| OCP-Tools-4.12-RHEL-8 | RedHat | jenkins-0:2.440.3.1716445200-3.el8 | * |
| OCP-Tools-4.12-RHEL-8 | RedHat | jenkins-2-plugins-0:4.12.1716445211-1.el8 | * |
| OCP-Tools-4.13-RHEL-8 | RedHat | jenkins-0:2.440.3.1716445150-3.el8 | * |
| OCP-Tools-4.13-RHEL-8 | RedHat | jenkins-2-plugins-0:4.13.1716445207-1.el8 | * |
| OCP-Tools-4.14-RHEL-8 | RedHat | jenkins-0:2.440.3.1716387933-3.el8 | * |
| OCP-Tools-4.14-RHEL-8 | RedHat | jenkins-2-plugins-0:4.14.1716388016-1.el8 | * |
| OCP-Tools-4.15-RHEL-8 | RedHat | jenkins-0:2.440.3.1718879390-3.el8 | * |
| OCP-Tools-4.15-RHEL-8 | RedHat | jenkins-2-plugins-0:4.15.1718879538-1.el8 | * |
| Red Hat build of Apache Camel 4.4.1 for Spring Boot 3.2 | RedHat | jetty | * |
| Red Hat build of Apicurio Registry 2.6.1 GA | RedHat | jetty | * |
| Jetty | Ubuntu | trusty | * |
| Jetty | Ubuntu | trusty/esm | * |
| Jetty | Ubuntu | xenial | * |
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://www.openwall.com/lists/oss-security/2024/03/20/2
- https://github.com/jetty/jetty.project/issues/11256
- https://github.com/jetty/jetty.project/security/advisories/GHSA-rggv-cv7r-mw98
- https://lists.debian.org/debian-lts-announce/2024/04/msg00002.html
- https://security.netapp.com/advisory/ntap-20240329-0001/
- http://www.openwall.com/lists/oss-security/2024/03/20/2
- https://github.com/jetty/jetty.project/issues/11256
- https://github.com/jetty/jetty.project/security/advisories/GHSA-rggv-cv7r-mw98
- https://lists.debian.org/debian-lts-announce/2024/04/msg00002.html
- https://security.netapp.com/advisory/ntap-20240329-0001/