CVE-2019-10072: High severity Apache Tomcat vulnerability

Published Jun 21, 2019
·
Updated

Apache Tomcat is vulnerable to a denial of service, caused by HTTP/2 connection window exhaustion on write. By failing to send WINDOWUPDATE messages, a remote attacker could exploit this vulnerability to block threads on the server and cause a denial of service.

Other sources

The fix for CVE-2019-0199 was incomplete and did not address HTTP/2 connection window exhaustion on write in Apache Tomcat versions 9.0.0.M1 to 9.0.19 and 8.5.0 to 8.5.40 . By not sending WINDOWUPDATE messages for the connection window (stream 0) clients were able to cause server-side threads to block eventually leading to thread exhaustion and a DoS.

The fix for CVE-2019-0199 was incomplete and did not address HTTP/2 connection window exhaustion on write. By not sending WINDOWUPDATE messages for the connection window (stream 0) clients were able to cause server-side threads to block eventually leading to thread exhaustion and a DoS.

References:

http://tomcat.apache.org/security-9.html#FixedinApacheTomcat9.0.20 http://tomcat.apache.org/security-8.html#FixedinApacheTomcat8.5.41 http://mail-archives.us.apache.org/modmbox/www-announce/201906.mbox/%3Cca69531a-1592-be7b-60ce-729549c7f812%40apache.org%3E

Upstream commits:

Tomcat 9.0: https://github.com/apache/tomcat/commit/7f748eb https://github.com/apache/tomcat/commit/ada725a

Tomcat 8.5 https://github.com/apache/tomcat/commit/0bcd69c https://github.com/apache/tomcat/commit/8d14c6f

Red Hat

Affected Software

80 affected componentsFixes available
redhat/jws5-ecj<0:4.12.0-1.redhat_1.1.el6
0:4.12.0-1.redhat_1.1.el6
redhat/jws5-javapackages-tools<0:3.4.1-5.15.11.el6
0:3.4.1-5.15.11.el6
redhat/jws5-jboss-logging<0:3.3.2-1.Final_redhat_00001.1.el6
0:3.3.2-1.Final_redhat_00001.1.el6
redhat/jws5-tomcat<0:9.0.21-10.redhat_4.1.el6
0:9.0.21-10.redhat_4.1.el6
redhat/jws5-tomcat-native<0:1.2.21-34.redhat_34.el6
0:1.2.21-34.redhat_34.el6
redhat/jws5-tomcat-vault<0:1.1.8-1.Final_redhat_1.1.el6
0:1.1.8-1.Final_redhat_1.1.el6
redhat/jws5-ecj<0:4.12.0-1.redhat_1.1.el7
0:4.12.0-1.redhat_1.1.el7
redhat/jws5-javapackages-tools<0:3.4.1-5.15.11.el7
0:3.4.1-5.15.11.el7
redhat/jws5-jboss-logging<0:3.3.2-1.Final_redhat_00001.1.el7
0:3.3.2-1.Final_redhat_00001.1.el7
redhat/jws5-tomcat<0:9.0.21-10.redhat_4.1.el7
0:9.0.21-10.redhat_4.1.el7
redhat/jws5-tomcat-native<0:1.2.21-34.redhat_34.el7
0:1.2.21-34.redhat_34.el7
redhat/jws5-tomcat-vault<0:1.1.8-1.Final_redhat_1.1.el7
0:1.1.8-1.Final_redhat_1.1.el7
redhat/jws5-ecj<0:4.12.0-1.redhat_1.1.el8
0:4.12.0-1.redhat_1.1.el8
redhat/jws5-javapackages-tools<0:3.4.1-5.15.11.el8
0:3.4.1-5.15.11.el8
redhat/jws5-jboss-logging<0:3.3.2-1.Final_redhat_00001.1.el8
0:3.3.2-1.Final_redhat_00001.1.el8
redhat/jws5-tomcat<0:9.0.21-10.redhat_4.1.el8
0:9.0.21-10.redhat_4.1.el8
redhat/jws5-tomcat-native<0:1.2.21-34.redhat_34.el8
0:1.2.21-34.redhat_34.el8
redhat/jws5-tomcat-vault<0:1.1.8-1.Final_redhat_1.1.el8
0:1.1.8-1.Final_redhat_1.1.el8
redhat/Apache Tomcat<9.0.20
9.0.20
redhat/Apache Tomcat<8.5.41
8.5.41
maven/org.apache.tomcat.embed:tomcat-embed-core>=8.5.0<8.5.41
8.5.41
maven/org.apache.tomcat.embed:tomcat-embed-core>=9.0.0.M1<9.0.20
9.0.20
Apache Tomcat>=8.5.0<=8.5.40
Apache Tomcat>=9.0.1<=9.0.19
Apache Tomcat=9.0.0-milestone1
Apache Tomcat=9.0.0-milestone10
Apache Tomcat=9.0.0-milestone11
Apache Tomcat=9.0.0-milestone12
Apache Tomcat=9.0.0-milestone13
Apache Tomcat=9.0.0-milestone14
Apache Tomcat=9.0.0-milestone15
Apache Tomcat=9.0.0-milestone16
Apache Tomcat=9.0.0-milestone17
Apache Tomcat=9.0.0-milestone18
Apache Tomcat=9.0.0-milestone19
Apache Tomcat=9.0.0-milestone2
Apache Tomcat=9.0.0-milestone20
Apache Tomcat=9.0.0-milestone21
Apache Tomcat=9.0.0-milestone22
Apache Tomcat=9.0.0-milestone23
Apache Tomcat=9.0.0-milestone24
Apache Tomcat=9.0.0-milestone25
Apache Tomcat=9.0.0-milestone26
Apache Tomcat=9.0.0-milestone27
Apache Tomcat=9.0.0-milestone3
Apache Tomcat=9.0.0-milestone4
Apache Tomcat=9.0.0-milestone5
Apache Tomcat=9.0.0-milestone6
Apache Tomcat=9.0.0-milestone7
Apache Tomcat=9.0.0-milestone8
Apache Tomcat=9.0.0-milestone9
Apache Tomcat=9.0.0-m1
Apache Tomcat=9.0.0-m10
Apache Tomcat=9.0.0-m11
Apache Tomcat=9.0.0-m12
Apache Tomcat=9.0.0-m13
Apache Tomcat=9.0.0-m14
Apache Tomcat=9.0.0-m15
Apache Tomcat=9.0.0-m16
Apache Tomcat=9.0.0-m17
Apache Tomcat=9.0.0-m18
Apache Tomcat=9.0.0-m19
Apache Tomcat=9.0.0-m2
Apache Tomcat=9.0.0-m20
Apache Tomcat=9.0.0-m21
Apache Tomcat=9.0.0-m22
Apache Tomcat=9.0.0-m23
Apache Tomcat=9.0.0-m24
Apache Tomcat=9.0.0-m25
Apache Tomcat=9.0.0-m26
Apache Tomcat=9.0.0-m27
Apache Tomcat=9.0.0-m3
Apache Tomcat=9.0.0-m4
Apache Tomcat=9.0.0-m5
Apache Tomcat=9.0.0-m6
Apache Tomcat=9.0.0-m7
Apache Tomcat=9.0.0-m8
Apache Tomcat=9.0.0-m9
IBM GDE<=3.0.0.2
debian/tomcat9
9.0.43-2~deb11u109.0.107-0+deb11u29.0.70-29.0.95-19.0.115-1

Remediation

Information

pki-servlet-container does not use HTTP/2 in its default configuration.

Event History

Jun 21, 2019
CVE Published
12:00 AM
CVE Published
via MITRE·05:56 PM
Data Sourced
via MITRE·05:56 PM
DescriptionWeakness
Jun 25, 2019
Data Sourced
via Red Hat·08:23 AM
DescriptionSeverityAffected Software
Jun 26, 2019
Advisory Published
via GitHub·01:09 AM
Feb 20, 2026
Data Sourced
via Ubuntu·09:34 PM
RemedyDescriptionSeverityAffected Software
Data Sourced
via Launchpad·09:35 PM
Description
Data Sourced
via Debian·09:35 PM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is CVE-2019-10072?

CVE-2019-10072 is a vulnerability in Apache Tomcat that allows clients to cause server-side threads to become exhausted.

2

What is the severity of CVE-2019-10072?

CVE-2019-10072 has a severity rating of 5.3 (Medium).

3

Which versions of Apache Tomcat are affected by CVE-2019-10072?

Apache Tomcat versions 9.0.0.M1 to 9.0.19 and 8.5.0 to 8.5.40 are affected by CVE-2019-10072.

4

How can I fix CVE-2019-10072?

Update your Apache Tomcat installation to version 9.0.20 or later (for 9.x) or version 8.5.41 or later (for 8.5.x).

5

Where can I find more information about CVE-2019-10072?

You can find more information about CVE-2019-10072 at the following references: - [CVE-2019-10072](https://www.cve.org/CVERecord?id=CVE-2019-10072) - [NVD](https://nvd.nist.gov/vuln/detail/CVE-2019-10072) - [Apache Tomcat Security](http://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.5.41) - [Bugzilla](https://bugzilla.redhat.com/show_bug.cgi?id=1723708) - [Red Hat Security Advisory](https://access.redhat.com/errata/RHSA-2019:3931)

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203