CVE-2017-5650

UnknownEPSS 8.28%

Last modified

CVE-2017-5650 is a vulnerability of currently unknown severity. 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. EPSS estimates a 8.28% chance of exploitation in the next 30 days.

Description

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.

Metrics

EPSS Probability
8.28%

94.2th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersionsUpdate
ApacheTomcat8.5.0
ApacheTomcat8.5.1
ApacheTomcat8.5.2
ApacheTomcat8.5.3
ApacheTomcat8.5.4
ApacheTomcat8.5.5
ApacheTomcat8.5.6
ApacheTomcat8.5.7
ApacheTomcat8.5.8
ApacheTomcat8.5.9
ApacheTomcat8.5.10
ApacheTomcat8.5.11
ApacheTomcat8.5.12
ApacheTomcat9.0.0Milestone1

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2017-5650?
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.
How severe is CVE-2017-5650?
Severity scoring for CVE-2017-5650 is pending analysis. The EPSS model estimates a 8.28% probability of exploitation in the next 30 days.
How do I fix CVE-2017-5650?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2017-5650?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST