7.5
CWE
400
Advisory Published
CVE Published
Advisory Published
Updated

CVE-2019-0199

First published: Mon Mar 25 2019(Updated: )

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.

Credit: security@apache.org security@apache.org security@apache.org

Affected SoftwareAffected VersionHow to fix
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
debian/tomcat9
9.0.31-1~deb10u6
9.0.31-1~deb10u10
9.0.43-2~deb11u6
9.0.43-2~deb11u9
9.0.70-2
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
redhat/tomcat<8.5.38
8.5.38
redhat/tomcat<9.0.16
9.0.16
Tomcat>=8.5.0<=8.5.37
Tomcat>=9.0.1<=9.0.14
Tomcat=9.0.0-milestone1
Tomcat=9.0.0-milestone10
Tomcat=9.0.0-milestone11
Tomcat=9.0.0-milestone12
Tomcat=9.0.0-milestone13
Tomcat=9.0.0-milestone14
Tomcat=9.0.0-milestone15
Tomcat=9.0.0-milestone16
Tomcat=9.0.0-milestone17
Tomcat=9.0.0-milestone18
Tomcat=9.0.0-milestone19
Tomcat=9.0.0-milestone2
Tomcat=9.0.0-milestone20
Tomcat=9.0.0-milestone21
Tomcat=9.0.0-milestone3
Tomcat=9.0.0-milestone4
Tomcat=9.0.0-milestone5
Tomcat=9.0.0-milestone6
Tomcat=9.0.0-milestone7
Tomcat=9.0.0-milestone8
Tomcat=9.0.0-milestone9
Tomcat=9.0.0-m1
Tomcat=9.0.0-m10
Tomcat=9.0.0-m11
Tomcat=9.0.0-m12
Tomcat=9.0.0-m13
Tomcat=9.0.0-m14
Tomcat=9.0.0-m15
Tomcat=9.0.0-m16
Tomcat=9.0.0-m17
Tomcat=9.0.0-m18
Tomcat=9.0.0-m19
Tomcat=9.0.0-m2
Tomcat=9.0.0-m20
Tomcat=9.0.0-m21
Tomcat=9.0.0-m3
Tomcat=9.0.0-m4
Tomcat=9.0.0-m5
Tomcat=9.0.0-m6
Tomcat=9.0.0-m7
Tomcat=9.0.0-m8
Tomcat=9.0.0-m9
IBM Global Data Engine<=3.0.0.2

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Reference Links

Parent vulnerabilities

(Appears in the following advisories)

Frequently Asked Questions

  • 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.

  • 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.

  • 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.

  • 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.

  • 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.

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203