CyberRota Analysis
AI-GeneratedEnvoy's optional oghttp2 upstream HTTP/2 codec is vulnerable to a flaw that allows it to accept a malformed response trailer HEADERS frame without END_STREAM, leading to a dangling reference in ClientStreamImpl. This can result in a crash of the Envoy process when a subsequent frame is dispatched through the freed object. Organizations using Envoy versions prior to 1.36.10, 1.37.6, 1.38.4, and 1.39.1, particularly those with oghttp2 enabled, should prioritize upgrading to mitigate this high-severity vulnerability.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Envoy is an open source edge and service proxy designed for cloud-native applications. Prior to 1.36.10, 1.37.6, 1.38.4, and 1.39.1, Envoy's optional oghttp2 upstream HTTP/2 codec accepts a response trailer HEADERS frame without END_STREAM. Envoy completes and deferred-deletes the ActiveRequest while oghttp2 keeps the stream open, leaving ClientStreamImpl with a dangling response_decoder_ reference. A later frame on the stream can dispatch through the freed object and crash the process. The relevant scope boundary is that the default nghttp2 codec rejects the malformed trailers, and the trigger is upstream-only with oghttp2 enabled. This issue is fixed in versions 1.36.10, 1.37.6, 1.38.4, and 1.39.1.
Related CVEs
Other vulnerabilities affecting the same vendor(s)