Eclipse Foundation Eclipse Jetty
A client may issue HTTP/2 requests to a Jetty server that result in blocking writes that are never unblocked, eventually causing all threads to be blocked and the whole server to become unresponsive. This is caused by a race condition in the server when handling RST_STREAM frames and GOAWAY frames sent by the client. The race condition "resets" the HTTP2Flusher.terminated, previously set to a non-null value, to the null value, allowing entries to be enqueued in the flusher that however will never be processed. These unprocessed entries are the ones that would unblock the write-blocked threads.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.7high · scored by CNA · CWE-400
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
Eclipse Foundation Eclipse Jetty
- >= 12.1.0, <= 12.1.10
- >= 12.0.0, <= 12.0.37
- >= 11.00, <= 11.0.31
- >= 10.0.0, <= 10.0.31
- >= 9.4.36, <= 9.4.63
Mitigation
The record names no fix. Check the vendor advisory below.
References
- Vendor advisory github.com/jetty/jetty.project/security/adviso…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.