CVE-2017-5650: High severity Apache Tomcat vulnerability
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 WINDOWUPDATE 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
maven/org.apache.tomcat:tomcatto a version that resolves this vulnerability.Fixed in 8.5.13 - Upgrade
Upgrade
maven/org.apache.tomcat:tomcatto a version that resolves this vulnerability.Fixed in 9.0.0.M19 - Upgrade
Upgrade
Apache Tomcatto a version that resolves this vulnerability.Fixed in 8.5.13 - Upgrade
Upgrade
Apache Tomcatto a version that resolves this vulnerability.Fixed in 9.0.0.M19
Event History
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.