Описание
Envoy is an open source edge and service proxy designed for cloud-native applications. From 1.18.0 until 1.35.13, 1.36.9, 1.37.5, and 1.38.3, the router filter contains a null pointer dereference vulnerability when handling HTTP 303 (See Other) internal redirects for body-less non-GET/HEAD requests. When a POST, PUT, DELETE, or PATCH request without a body is sent to a route configured with internal redirect policy that includes 303 in redirect_response_codes, and the upstream responds with HTTP 303, the redirect handling code attempts to drain a request body buffer that was never allocated. This results in a segmentation fault that crashes the entire Envoy process. When route configured with internal_redirect_policy including 303 in redirect_response_codes and upstream must return HTTP 303 response, an unauthenticated attacker can exploit this to cause complete denial of service, terminating all active connections. This vulnerability is fixed in 1.35.13, 1.36.9, 1.37.5, and 1.38.3.
A flaw was found in Envoy. An unauthenticated attacker can exploit a null pointer dereference vulnerability in the router filter. This occurs when handling HTTP 303 (See Other) internal redirects for body-less non-GET/HEAD requests. By sending a POST, PUT, DELETE, or PATCH request without a body to a specially configured route, and if the upstream responds with HTTP 303, the Envoy process will crash. This leads to a complete denial of service, terminating all active connections.
Отчет
Moderate: An unauthenticated attacker can trigger a denial of service in Envoy. This is due to a null pointer dereference when handling HTTP 303 internal redirects for body-less non-GET/HEAD requests, leading to a crash of the Envoy process. This vulnerability affects Envoy deployments configured with an internal redirect policy that includes HTTP 303 in redirect_response_codes.
Меры по смягчению последствий
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.
Затронутые пакеты
| Платформа | Пакет | Состояние | Рекомендация | Релиз |
|---|---|---|---|---|
| OpenShift Service Mesh 2 | openshift-service-mesh/proxyv2-rhel9 | Will not fix | ||
| Red Hat OpenShift Service Mesh 3.0 | openshift-service-mesh/istio-proxyv2-rhel9 | Fixed | RHSA-2026:49705 | 03.08.2026 |
| Red Hat OpenShift Service Mesh 3.1 | openshift-service-mesh/istio-proxyv2-rhel9 | Fixed | RHSA-2026:49729 | 03.08.2026 |
| Red Hat OpenShift Service Mesh 3.2 | openshift-service-mesh/istio-proxyv2-rhel9 | Fixed | RHSA-2026:49744 | 03.08.2026 |
| Red Hat OpenShift Service Mesh 3.3 | openshift-service-mesh/istio-proxyv2-rhel9 | Fixed | RHSA-2026:49765 | 03.08.2026 |
Показывать по
Дополнительная информация
Статус:
EPSS
5.9 Medium
CVSS3
Связанные уязвимости
Envoy is an open source edge and service proxy designed for cloud-native applications. From 1.18.0 until 1.35.13, 1.36.9, 1.37.5, and 1.38.3, the router filter contains a null pointer dereference vulnerability when handling HTTP 303 (See Other) internal redirects for body-less non-GET/HEAD requests. When a POST, PUT, DELETE, or PATCH request without a body is sent to a route configured with internal redirect policy that includes 303 in redirect_response_codes, and the upstream responds with HTTP 303, the redirect handling code attempts to drain a request body buffer that was never allocated. This results in a segmentation fault that crashes the entire Envoy process. When route configured with internal_redirect_policy including 303 in redirect_response_codes and upstream must return HTTP 303 response, an unauthenticated attacker can exploit this to cause complete denial of service, terminating all active connections. This vulnerability is fixed in 1.35.13, 1.36.9, 1.37.5, and 1.38.3.
Envoy is an open source edge and service proxy designed for cloud-nati ...
EPSS
5.9 Medium
CVSS3