First published: Fri Sep 20 2024(Updated: )
Envoy is a cloud-native high-performance edge/middle/service proxy. Envoy will crash when the http async client is handling `sendLocalReply` under some circumstance, e.g., websocket upgrade, and requests mirroring. The http async client will crash during the `sendLocalReply()` in http async client, one reason is http async client is duplicating the status code, another one is the destroy of router is called at the destructor of the async stream, while the stream is deferred deleted at first. There will be problems that the stream decoder is destroyed but its reference is called in `router.onDestroy()`, causing segment fault. This will impact ext_authz if the `upgrade` and `connection` header are allowed, and request mirrorring. This issue has been addressed in versions 1.31.2, 1.30.6, 1.29.9, and 1.28.7. Users are advised to upgrade. There are no known workarounds for this vulnerability.
Affected Software | Affected Version | How to fix |
---|---|---|
Envoy Proxy | <1.28.7 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-2313687 can vary based on the specific deployment and usage scenarios of Envoy Proxy.
To fix REDHAT-BUG-2313687, you should upgrade Envoy Proxy to version 1.28.7 or later to avoid the crashing issue.
REDHAT-BUG-2313687 affects Envoy Proxy versions prior to 1.28.7.
The crash in REDHAT-BUG-2313687 is caused when the HTTP async client handles `sendLocalReply` under specific circumstances like websocket upgrades.
Currently, there are no documented workarounds for REDHAT-BUG-2313687; updating to a fixed version is recommended.