First published: Thu Sep 19 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.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Envoy Proxy | <1.28.7 | |
Envoy Proxy | >=1.29.0<1.29.9 | |
Envoy Proxy | >=1.30.0<1.30.6 | |
Envoy Proxy | >=1.31.0<1.31.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-45810 has a critical severity as it can lead to crashes in the Envoy proxy under certain conditions.
To fix CVE-2024-45810, upgrade Envoy Proxy to version 1.28.7 or later, or to a version that is not affected in the specified ranges.
CVE-2024-45810 affects Envoy versions prior to 1.28.7, between 1.29.0 and 1.29.9, between 1.30.0 and 1.30.6, and between 1.31.0 and 1.31.2.
Symptoms of CVE-2024-45810 may include unexpected crashes of the Envoy proxy service during websocket upgrades and request mirroring processes.
Yes, CVE-2024-45810 is considered a remote vulnerability as it can potentially be exploited by remote attackers through crafted requests.