Envoy Proxy Can Crash with Malformed Rate Limit Configuration

Summary

Envoy Proxy versions prior to 1.37.1, 1.36.5, 1.35.8, and 1.34.13 may crash if an attacker sends a malformed rate limit request. This can happen when both request and response rate limits are enabled. To fix, upgrade to the latest version.

What to do

No fix is available yet. Check with your software vendor for updates.

Affected software

Vendor	Product	Affected versions	Fix available
envoyproxy	envoy	<= 1.34.13	–
envoyproxy	envoy	> 1.35.0 , <= 1.35.8	–
envoyproxy	envoy	> 1.36.0 , <= 1.36.5	–
envoyproxy	envoy	1.37.0	–
github.com	envoyproxy	1.37.0	–
github.com	envoyproxy	> 1.36.0 , <= 1.36.4	–
envoyproxy	github.com/envoyproxy/envoy	All versions	–
envoyproxy	github.com/envoyproxy/envoy	> 1.36.0 , <= 1.36.4	–

Original title

Envoy is a high-performance edge/middle/service proxy. Prior to 1.37.1, 1.36.5, 1.35.8, and 1.34.13, At the rate limit filter, if the response phase limit with apply_on_stream_done in the rate limi...

Original description

Envoy is a high-performance edge/middle/service proxy. Prior to 1.37.1, 1.36.5, 1.35.8, and 1.34.13, At the rate limit filter, if the response phase limit with apply_on_stream_done in the rate limit configuration is enabled and the response phase limit request fails directly, it may crash Envoy. When both the request phase limit and response phase limit are enabled, the safe gRPC client instance will be re-used for both the request phase request and response phase request. But after the request phase request is done, the inner state of the request phase limit request in gRPC client is not cleaned up. When a second limit request is sent at response phase, and the second limit request fails directly, the previous request's inner state may be accessed and result in crash. This vulnerability is fixed in 1.37.1, 1.36.5, 1.35.8, and 1.34.13.

ghsa CVSS3.1 5.3

Vulnerability type

CWE-416 Use After Free