First published: Fri Feb 09 2024(Updated: )
Envoy is a high-performance edge/middle/service proxy. Envoy crashes in Proxy protocol when using an address type that isn’t supported by the OS. Envoy is susceptible to crashing on a host with IPv6 disabled and a listener config with proxy protocol enabled when it receives a request where the client presents its IPv6 address. It is valid for a client to present its IPv6 address to a target server even though the whole chain is connected via IPv4. This issue has been addressed in released 1.29.1, 1.28.1, 1.27.3, and 1.26.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.26.0<1.26.7 | |
Envoy Proxy | >=1.27.0<1.27.3 | |
Envoy Proxy | >=1.28.0<1.28.1 | |
Envoy Proxy | >=1.29.0<1.29.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-23325 has been classified as a high severity vulnerability due to its potential to crash Envoy under specific configurations.
To fix CVE-2024-23325, you should update Envoy to a version above 1.29.1, 1.28.1, 1.27.3, or 1.26.7, as appropriate for your current version.
CVE-2024-23325 affects Envoy versions from 1.26.0 to 1.26.7, 1.27.0 to 1.27.3, 1.28.0 to 1.28.1, and 1.29.0 to 1.29.1.
CVE-2024-23325 is triggered when Envoy receives a proxy protocol request while IPv6 is disabled on the host, leading to a crash.
Currently, disabling the proxy protocol or enabling IPv6 on the host can serve as a temporary workaround for CVE-2024-23325.