Apache Tomcat Denial of Service vulnerability
Apache Tomcat
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.tomcat.embed:tomcat-embed-core Maven |
|
|
| org.apache.tomcat:tomcat-coyote Maven |
|
Apache Tomcat
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.tomcat.embed:tomcat-embed-core Maven |
|
|
| org.apache.tomcat:tomcat-coyote Maven |
|
|
The HTTP/2 implementation in Apache Tomcat 9.0.0.M1 to 9.0.14 and 8.5.0 to 8.5.37 accepted streams with excessive numbers of SETTINGS frames and also permitted clients to keep streams open without reading/writing request/response data. By keeping streams open for requests that utilised the Servlet API's blocking I/O, clients were able to cause server-side threads to block eventually leading to thread exhaustion and a DoS.
From the CVE record · apache
Apache Tomcat’s HTTP/2 implementation accepts excessive SETTINGS frames and allows clients to keep streams open without exchanging request or response data. A network client can keep streams using the Servlet API’s blocking I/O open until server-side threads are exhausted, causing a denial of service.
Check Apache Tomcat deployments running 9.0.0.M1 through 9.0.14 or 8.5.0 through 8.5.37, including affected Maven tomcat-embed-core and tomcat-coyote packages before 9.0.16 or 8.5.38.