Envoy
Envoy ext_authz: request `:path` pseudoheader dereferenced w/o null check
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 ext_authz filter assumes that a request contains a :path pseudoheader when applying query_parameters_to_set or query_parameters_to_remove from an authorization response. A path-less CONNECT request makes request_headers_->Path() return null, and Filter::onComplete dereferences that pointer while parsing the query string. An unauthenticated downstream client can crash the Envoy process when the filter and authorization response use query-parameter mutation. The relevant scope boundary is that the deployment must accept path-less CONNECT and configure ext_authz query-parameter mutation. This issue is fixed in versions 1.36.10, 1.37.6, 1.38.4, and 1.39.1.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 1.36.10
- >= 1.37.0, < 1.37.6
- >= 1.38.0, < 1.38.4
- >= 1.39.0, < 1.39.1
Fixed in 1.36.10, 1.37.6, 1.38.4, 1.39.1
Mitigation
Upgrade envoy to 1.36.10 or 1.37.6 or 1.38.4 or 1.39.1 or later.
References
- Vendor advisory github.com/envoyproxy/envoy/security/advisorie…
- Patch github.com/envoyproxy/envoy/commit/064af2e61d0…
- Patch github.com/envoyproxy/envoy/commit/5f3b8e9b2b8…
5 more
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.