Envoy RELEASE_ASSERT using auto_sni with :authority header > 255 bytes
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 1.27.5, 1.28.3 and 1.29.4.
Envoy is a cloud-native, open source edge and service proxy. When an upstream TLS cluster is used with `auto_sni` enabled, a request containing a `host`/`:authority` header longer than 255 characters triggers an abnormal termination of Envoy process. Envoy does not gracefully handle an error when setting SNI for outbound TLS connection. The error can occur when Envoy attempts to use the `host`/`:authority` header value longer than 255 characters as SNI for outbound TLS connection. SNI length is limited to 255 characters per the standard. Envoy always expects this operation to succeed and abnormally aborts the process when it fails. This vulnerability is fixed in 1.30.1, 1.29.4, 1.28.3, and 1.27.5.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| envoyproxy | envoy | >=1.13.0 <1.27.5, >=1.28.0 <1.28.3, >=1.29.0 <1.29.4, =1.30.0 | 1.27.5, 1.28.3, 1.29.4 |
| envoyproxy | >=1.13.0 <1.27.5, >=1.28.0 <1.28.3, >=1.29.0 <1.29.4, >=1.30.0 <1.30.1 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket