CVE-2024-39305: Envoy Proxy use after free when route hash policy is configured with cookie attributes
Envoy is a cloud-native, open source edge and service proxy. Prior to versions 1.30.4, 1.29.7, 1.28.5, and 1.27.7. Envoy references already freed memory when route hash policy is configured with cookie attributes. Note that this vulnerability has been fixed in the open as the effect would be immediately apparent if it was configured. Memory allocated for holding attribute values is freed after configuration was parsed. During request processing Envoy will attempt to copy content of de-allocated memory into request cookie header. This can lead to arbitrary content of Envoy's memory to be sent to the upstream service or abnormal process termination. This vulnerability is fixed in Envoy versions v1.30.4, v1.29.7, v1.28.5, and v1.27.7. As a workaround, do not use cookie attributes in route action hash policy.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-39305?
CVE-2024-39305 is considered a moderate severity vulnerability due to memory management issues leading to potential application instability.
How do I fix CVE-2024-39305?
To fix CVE-2024-39305, upgrade Envoy to version 1.30.4 or later, or 1.29.7 or later, or 1.28.5 or later, or 1.27.7 or later.
What versions are affected by CVE-2024-39305?
CVE-2024-39305 affects Envoy versions prior to 1.30.4, 1.29.7, 1.28.5, and 1.27.7.
What impact does CVE-2024-39305 have on Envoy?
CVE-2024-39305 can cause Envoy to reference already freed memory, potentially leading to crashes or unexpected behaviors.
Is there a known exploit for CVE-2024-39305?
As of now, there are no public exploits specifically targeting CVE-2024-39305.