Envoy has an RBAC Header Validation Bypass via Multi-Value Header Concatenation
envoyproxy envoy
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/envoyproxy/envoy Go |
|
|
envoyproxy envoy
| Product | Affected | Fixed in |
|---|---|---|
| github.com/envoyproxy/envoy Go |
|
|
Envoy is a high-performance edge/middle/service proxy. Prior to 1.37.1, 1.36.5, 1.35.8, and 1.34.13, the Envoy RBAC (Role-Based Access Control) filter contains a logic vulnerability in how it validates HTTP headers when multiple values are present for the same header name. Instead of validating each header value individually, Envoy concatenates all values into a single comma-separated string. This behavior allows attackers to bypass RBAC policies—specifically "Deny" rules—by sending duplicate headers, effectively obscuring the malicious value from exact-match mechanisms. This vulnerability is fixed in 1.37.1, 1.36.5, 1.35.8, and 1.34.13.
From the CVE record · GitHub_M
Envoy’s RBAC filter concatenates duplicate HTTP header values before checking them against policies. An attacker who can send HTTP requests with duplicate headers can bypass exact-match Deny rules. The input does not specify whether authentication is required.
Check deployments using Envoy or the Go package github.com/envoyproxy/envoy in the affected ranges: >=1.37.0 <1.37.1, >=1.36.0 <1.36.5, >=1.35.0 <1.35.9, or <1.34.13.