Description
Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Prior to versions 1.17.14, 1.18.8, and 1.19.2, Ingress Network Policies are not enforced for traffic from pods to L7 Services (Envoy, GAMMA) with a local backend on the same node, when Per-Endpoint Routing is enabled and BPF Host Routing is disabled. Per-Endpoint Routing is disabled by default, but is automatically enabled in deployments using cloud IPAM, including Cilium ENI on EKS (`eni.enabled`), AlibabaCloud ENI (`alibabacloud.enabled`), Azure IPAM (`azure.enabled`, but not AKS BYOCNI), and some GKE deployments (`gke.enabled`; managed offerings such as GKE Dataplane V2 may use different defaults). It is typically not enabled in tunneled deployments, and chaining deployments are not affected. In practice, Amazon EKS with Cilium ENI mode is likely the most common affected environment. Versions 1.17.14, 1.18.8, and 1.19.2 contain a patch. There is currently no officially verified or comprehensive workaround for this issue. The only option would be to disable per-endpoint routes, but this will likely cause disruptions to ongoing connections, and potential conflicts if running in cloud providers.
Problem types
CWE-284: Improper Access Control
CWE-863: Incorrect Authorization
Product status
>= 1.18.0, < 1.18.8
>= 1.19.0, < 1.19.2
References
github.com/...cilium/security/advisories/GHSA-hxv8-4j4r-cqgv
github.com/cilium/cilium/pull/44693
docs.cilium.io/en/stable/network/concepts/routing/
docs.cilium.io/en/stable/network/kubernetes/policy/
docs.cilium.io/.../network/servicemesh/l7-traffic-management
docs.cilium.io/en/stable/operations/performance/tuning/