Описание
Quarkus is a Cloud Native, (Linux) Container First framework for writing Java applications. Prior to versions 3.31.0, 3.27.2, and 3.20.5, 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. This issue has been patched in versions 3.31.0, 3.27.2, and 3.20.5. A workaround involves implementing a health check that monitors the status and saturation of the worker thread pool to detect abnormal thread retention early.
A flaw was found in the Quarkus REST HTTP layer. This vulnerability allows remote attackers to cause an application level denial of service by repeatedly dropping client connections while response chunks are being transmitted, leading to worker thread exhaustion.
Отчет
This vulnerability is rated Moderate for Red Hat products utilizing Quarkus REST, including Red Hat AMQ, Cryostat, Enterprise Application Platform, OpenShift Container Platform, and Red Hat Build of Quarkus. The flaw in the HTTP layer can lead to an application-level denial of service if remote attackers repeatedly drop client connections while response chunks are being transmitted, causing worker threads to become permanently blocked and exhausted.
Меры по смягчению последствий
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Затронутые пакеты
| Платформа | Пакет | Состояние | Рекомендация | Релиз |
|---|---|---|---|---|
| Cryostat 4 | quarkus-rest | Fix deferred | ||
| Red Hat build of Debezium 3 | quarkus-rest | Fix deferred | ||
| Red Hat JBoss Enterprise Application Platform 8 | quarkus-rest | Fix deferred | ||
| Red Hat JBoss Enterprise Application Platform Expansion Pack | quarkus-rest | Fix deferred | ||
| Red Hat OpenShift Container Platform 4 | openshift4/insights-runtime-exporter-rhel9 | Fix deferred | ||
| Red Hat OpenShift Container Platform 4 | openshift4/insights-runtime-extractor-rhel9 | Fix deferred | ||
| streams for Apache Kafka 2 | quarkus-rest | Fix deferred | ||
| streams for Apache Kafka 3 | quarkus-rest | Fix deferred | ||
| Red Hat build of Quarkus 3.20.5 | quarkus-rest | Fixed | RHSA-2026:1899 | 05.02.2026 |
| Red Hat build of Quarkus 3.27.2 | quarkus-rest | Fixed | RHSA-2026:1965 | 05.02.2026 |
Показывать по
Дополнительная информация
Статус:
EPSS
5.9 Medium
CVSS3
Связанные уязвимости
Quarkus is a Cloud Native, (Linux) Container First framework for writing Java applications. Prior to versions 3.31.0, 3.27.2, and 3.20.5, 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. This issue has been patched in versions 3.31.0, 3.27.2, and 3.20.5. A workaround involves implementing a health check that monitors the status and saturation of the worker thread pool to detect abnormal thread retention early.
Quarkus REST has potential worker thread starvation when HTTP connection is closed while waiting to write
EPSS
5.9 Medium
CVSS3