GHSA-5rfx-cp42-p624
Quarkus REST has potential worker thread starvation when HTTP connection is closed while waiting to write
Packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| Maven | io.quarkus:quarkus-rest | < 3.20.5 | 3.20.5 |
| Maven | io.quarkus:quarkus-rest | >= 3.21.0, < 3.27.2 | 3.27.2 |
| Maven | io.quarkus:quarkus-rest | >= 3.30.0, < 3.31.0 | 3.31.0 |
Details
As written in the advisory (Markdown source, shown as plain text).
A vulnerability exists in the HTTP layer of Quarkus REST related to response handling. When a response is being written, the framework waits for previously written response chunks to be fully transmitted before proceeding. If the client connection is dropped during this waiting period, the associated worker thread is never released and becomes permanently blocked. Under sustained or repeated occurrences, this can exhaust the available worker threads, leading to degraded performance, or complete unavailability of the application.
## Workarounds
For versions without the fix applied, it is recommended to implement a health check that monitors the status and saturation of the worker thread pool. This helps detect abnormal thread retention early and allows operators to take corrective action before the application’s responsiveness is impacted.
## Credits
CVE reported by Shaswata Jash, Nokia
References
External links from the advisory. They lead to third-party sites.