CVE-2019-0199: High severity Apache Tomcat vulnerability

Published Mar 25, 2019
·
Updated

A flaw was found in Apache Tomcat, where the HTTP/2 implementation accepted streams with excessive numbers of SETTINGS frames and also permitted clients to keep streams open, which enables them to cause server-side threads to block. This flaw eventually leads to a denial of service attack.

Other sources

A vulnerability was found in Apache Tomcat version from 9.0.0.M1 to 9.0.14 inclusive and 8.5.0 to 8.5.37 inclusive. The HTTP/2 implementation 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.

References: https://mail-archives.apache.org/modmbox/tomcat-announce/201903.mbox/browser http://tomcat.apache.org/security-9.html http://tomcat.apache.org/security-8.html

— Red Hat

Apache Tomcat is vulnerable to a denial of service, caused by the acceptance of streams with excessive numbers of SETTINGS frames and the permitting of clients to keep streams open without reading/writing request data by the HTTP/2 implementation. By sending excessive SETTINGS frames, a remote attacker could exploit this vulnerability to cause a denial of service.

— IBM

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.

Affected Software

68 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
maven/org.apache.tomcat.embed:tomcat-embed-core>=8.0.0<8.5.38
8.5.38
maven/org.apache.tomcat.embed:tomcat-embed-core>=9.0.0<9.0.16
9.0.16
Apache Tomcat>=8.5.0<=8.5.37
Apache Tomcat>=9.0.1<=9.0.14
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-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-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
redhat/tomcat<8.5.38
8.5.38
redhat/tomcat<9.0.16
9.0.16
debian/tomcat9
9.0.70-29.0.95-19.0.122-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/jws5-ecj to a version that resolves this vulnerability.

    Fixed in 0:4.12.0-1.redhat_1.1.el6
  2. Upgrade

    Upgrade redhat/jws5-javapackages-tools to a version that resolves this vulnerability.

    Fixed in 0:3.4.1-5.15.11.el6
  3. Upgrade

    Upgrade redhat/jws5-jboss-logging to a version that resolves this vulnerability.

    Fixed in 0:3.3.2-1.Final_redhat_00001.1.el6
  4. Upgrade

    Upgrade redhat/jws5-tomcat to a version that resolves this vulnerability.

    Fixed in 0:9.0.21-10.redhat_4.1.el6
  5. Upgrade

    Upgrade redhat/jws5-tomcat-native to a version that resolves this vulnerability.

    Fixed in 0:1.2.21-34.redhat_34.el6
  6. Upgrade

    Upgrade redhat/jws5-tomcat-vault to a version that resolves this vulnerability.

    Fixed in 0:1.1.8-1.Final_redhat_1.1.el6
  7. Upgrade

    Upgrade redhat/jws5-ecj to a version that resolves this vulnerability.

    Fixed in 0:4.12.0-1.redhat_1.1.el7
  8. Upgrade

    Upgrade redhat/jws5-javapackages-tools to a version that resolves this vulnerability.

    Fixed in 0:3.4.1-5.15.11.el7
  9. Upgrade

    Upgrade redhat/jws5-jboss-logging to a version that resolves this vulnerability.

    Fixed in 0:3.3.2-1.Final_redhat_00001.1.el7
  10. Upgrade

    Upgrade redhat/jws5-tomcat to a version that resolves this vulnerability.

    Fixed in 0:9.0.21-10.redhat_4.1.el7
  11. Upgrade

    Upgrade redhat/jws5-tomcat-native to a version that resolves this vulnerability.

    Fixed in 0:1.2.21-34.redhat_34.el7
  12. Upgrade

    Upgrade redhat/jws5-tomcat-vault to a version that resolves this vulnerability.

    Fixed in 0:1.1.8-1.Final_redhat_1.1.el7
  13. Upgrade

    Upgrade redhat/jws5-ecj to a version that resolves this vulnerability.

    Fixed in 0:4.12.0-1.redhat_1.1.el8
  14. Upgrade

    Upgrade redhat/jws5-javapackages-tools to a version that resolves this vulnerability.

    Fixed in 0:3.4.1-5.15.11.el8
  15. Upgrade

    Upgrade redhat/jws5-jboss-logging to a version that resolves this vulnerability.

    Fixed in 0:3.3.2-1.Final_redhat_00001.1.el8
  16. Upgrade

    Upgrade redhat/jws5-tomcat to a version that resolves this vulnerability.

    Fixed in 0:9.0.21-10.redhat_4.1.el8
  17. Upgrade

    Upgrade redhat/jws5-tomcat-native to a version that resolves this vulnerability.

    Fixed in 0:1.2.21-34.redhat_34.el8
  18. Upgrade

    Upgrade redhat/jws5-tomcat-vault to a version that resolves this vulnerability.

    Fixed in 0:1.1.8-1.Final_redhat_1.1.el8
  19. Upgrade

    Upgrade maven/org.apache.tomcat.embed:tomcat-embed-core to a version that resolves this vulnerability.

    Fixed in 8.5.38
  20. Upgrade

    Upgrade maven/org.apache.tomcat.embed:tomcat-embed-core to a version that resolves this vulnerability.

    Fixed in 9.0.16
  21. Upgrade

    Upgrade redhat/tomcat to a version that resolves this vulnerability.

    Fixed in 8.5.38
  22. Upgrade

    Upgrade redhat/tomcat to a version that resolves this vulnerability.

    Fixed in 9.0.16
  23. Upgrade

    Upgrade debian/tomcat9 to a version that resolves this vulnerability.

    Fixed in 9.0.70-2Fixed in 9.0.95-1Fixed in 9.0.122-1

Event History

Mar 25, 2019
CVE Published
12:00 AM
Mar 27, 2019
Data Sourced
via Red Hat·02:40 PM
DescriptionSeverityAffected Software
Apr 10, 2019
CVE Published
via MITRE·02:21 PM
Data Sourced
via MITRE·02:21 PM
DescriptionWeakness
Jun 15, 2020
Advisory Published
06:51 PM

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2019-0199?

CVE-2019-0199 is considered a high severity vulnerability due to the potential for denial of service exploits through excessive SETTINGS frames in HTTP/2.

2

How do I fix CVE-2019-0199?

To fix CVE-2019-0199, upgrade Apache Tomcat to version 8.5.38 or 9.0.16 or later.

3

What versions of Apache Tomcat are affected by CVE-2019-0199?

CVE-2019-0199 affects Apache Tomcat versions 9.0.0.M1 to 9.0.14 and 8.5.0 to 8.5.37.

4

What are the consequences of not addressing CVE-2019-0199?

Failing to address CVE-2019-0199 may lead to potential denial of service through unresponsive streams on affected Apache Tomcat servers.

5

Is there a workaround for CVE-2019-0199?

There are no known workarounds for CVE-2019-0199; updating to the patched versions is recommended for mitigation.

Company

Resources

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