Описание
In Apache Tomcat 9.0.0.M1 to 9.0.0.M18 and 8.5.0 to 8.5.12, the handling of an HTTP/2 GOAWAY frame for a connection did not close streams associated with that connection that were currently waiting for a WINDOW_UPDATE before allowing the application to write more data. These waiting streams each consumed a thread. A malicious client could therefore construct a series of HTTP/2 requests that would consume all available processing threads.
Затронутые пакеты
Платформа | Пакет | Состояние | Рекомендация | Релиз |
---|---|---|---|---|
Red Hat Enterprise Linux 5 | tomcat5 | Not affected | ||
Red Hat Enterprise Linux 6 | tomcat6 | Not affected | ||
Red Hat Enterprise Linux 7 | tomcat | Not affected | ||
Red Hat JBoss BRMS 5 | jbossweb | Not affected | ||
Red Hat JBoss Data Grid 6 | jbossweb | Not affected | ||
Red Hat JBoss Data Virtualization 6 | jbossweb | Not affected | ||
Red Hat JBoss Enterprise Application Platform 5 | jbossweb | Not affected | ||
Red Hat JBoss Enterprise Application Platform 6 | tomcat7 | Not affected | ||
Red Hat JBoss Enterprise Web Server 2 | tomcat6 | Not affected | ||
Red Hat JBoss Enterprise Web Server 2 | tomcat7 | Not affected |
Показывать по
Дополнительная информация
Статус:
EPSS
7.5 High
CVSS3
Связанные уязвимости
In Apache Tomcat 9.0.0.M1 to 9.0.0.M18 and 8.5.0 to 8.5.12, the handling of an HTTP/2 GOAWAY frame for a connection did not close streams associated with that connection that were currently waiting for a WINDOW_UPDATE before allowing the application to write more data. These waiting streams each consumed a thread. A malicious client could therefore construct a series of HTTP/2 requests that would consume all available processing threads.
In Apache Tomcat 9.0.0.M1 to 9.0.0.M18 and 8.5.0 to 8.5.12, the handling of an HTTP/2 GOAWAY frame for a connection did not close streams associated with that connection that were currently waiting for a WINDOW_UPDATE before allowing the application to write more data. These waiting streams each consumed a thread. A malicious client could therefore construct a series of HTTP/2 requests that would consume all available processing threads.
In Apache Tomcat 9.0.0.M1 to 9.0.0.M18 and 8.5.0 to 8.5.12, the handli ...
Improper Resource Shutdown or Release in Apache Tomcat
EPSS
7.5 High
CVSS3