7.5
CWE
404
Advisory Published
Advisory Published
Updated

CVE-2017-5650

First published: Mon Apr 17 2017(Updated: )

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.

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

Affected SoftwareAffected VersionHow to fix
maven/org.apache.tomcat:tomcat>=8.5.0<=8.5.12
8.5.13
maven/org.apache.tomcat:tomcat>=9.0.0.M1<=9.0.0.M18
9.0.0.M19
Tomcat=8.5.0
Tomcat=8.5.1
Tomcat=8.5.2
Tomcat=8.5.3
Tomcat=8.5.4
Tomcat=8.5.5
Tomcat=8.5.6
Tomcat=8.5.7
Tomcat=8.5.8
Tomcat=8.5.9
Tomcat=8.5.10
Tomcat=8.5.11
Tomcat=8.5.12
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-milestone2
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-m2
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

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

Frequently Asked Questions

  • What is the severity of CVE-2017-5650?

    CVE-2017-5650 has a medium severity rating due to potential denial of service vulnerabilities affecting Apache Tomcat.

  • How do I fix CVE-2017-5650?

    To fix CVE-2017-5650, upgrade to Apache Tomcat version 8.5.13 or 9.0.0.M19 or later.

  • What versions of Apache Tomcat are affected by CVE-2017-5650?

    CVE-2017-5650 affects Apache Tomcat versions 9.0.0.M1 to 9.0.0.M18 and 8.5.0 to 8.5.12.

  • Can CVE-2017-5650 cause denial of service attacks?

    Yes, CVE-2017-5650 can lead to denial of service conditions by not properly handling certain HTTP/2 frames.

  • Is it necessary to update if I am using an affected version of Tomcat?

    Yes, it is essential to update to a non-affected version to mitigate the vulnerabilities described in CVE-2017-5650.

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