Skip to content

GHSA-wc5v-r48v-g4vh

Cilium host policy bypass in endpoint-routes mode with dual-stack

Low Go
Severity
3.3 / 10
Low · CVSS 3.1
Exploit chance (EPSS)
—
No score published
Known exploited
No
Not in CISA's catalog
Weakness
—
Not classified
Fix
1.10.13
Upgrade github.com/cilium/cilium to this version or later

Description

Impact

This vulnerability allows bypassing host policies for IPv6 traffic coming from a Cilium-managed pod and destined to the host-network namespace (e.g., to a host-network pod). Host policy enforcement on IPv4 or for traffic coming from outside the node is not affected.

Cilium is only affected by this vulnerability if IPv4, IPv6, endpoint routes, and the host firewall are enabled. Note that endpoint routes are typically only enabled in GKE, EKS, AKS, and OpenShift; in those environments, IPv6 is typically disabled. Host firewall is disabled by default.

Patches

The bug is fixed in versions v1.10.13 and v1.11.7 of Cilium.

Workarounds

For affected users who can't upgrade, one potential workaround is to ensure all pods have network policies that prevent sending arbitrary traffic to the local node.

References

Commit fixing the vulnerability: https://github.com/cilium/cilium/commit/c758da7e9d19cd19b96dc90424c0b5ec7409cd0a.

For more information

If you have any questions or comments about this advisory, please reach out on Slack.

As usual, if you think you found a related vulnerability, we strongly encourage you to report security vulnerabilities to our private security mailing list: security@cilium.io—first, before disclosing them in any public forums. This is a private mailing list where only members of the Cilium internal security team are subscribed to, and is treated as top priority.

Affected versions

Go

PackageVulnerableFixed in
github.com/cilium/cilium
< 1.10.13
1.10.13
github.com/cilium/cilium
>= 1.11.0, < 1.11.7
1.11.7

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

github.com/cilium/cilium Go → 1.10.13

go
go get github.com/cilium/cilium@v1.10.13 && go mod tidy

Severity breakdown

CVSS 3.1 3.3

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

References

Timeline

  1. Published
  2. Last updated by the source
AdvisorySeverityWhy it's related
GHSA-fm8w-2m5w-9j7r
Cilium may unexpectedly allow ingress traffic from the local namespace when a Kubernetes NetworkPolicy is configured with an ipBlock match
Medium Also affects github.com/cilium/cilium
GHSA-w7c2-w76w-5hmj
Cilium: Namespaced HTTPRoutes can redirect traffic to other namespaces
High Also affects github.com/cilium/cilium
GHSA-q6h5-q3q6-f87x
CiliumLocalRedirectPolicy addressMatcher allows cross-namespace service traffic hijacking and can break service translation
Medium Also affects github.com/cilium/cilium
GHSA-3fcv-jvfp-m4q9
Cilium vulnerable to sensitive information disclosure and cluster disruption via local Envoy admin socket access
High Also affects github.com/cilium/cilium
GHSA-gj49-89wh-h4gj
Cillium exposes sensitive information included in the cilium-bugtool debug archive
Medium Also affects github.com/cilium/cilium
GHSA-hxv8-4j4r-cqgv
Cilium L7 proxy may bypass Kubernetes NetworkPolicy for same-node traffic
Medium Also affects github.com/cilium/cilium
GHSA-5r23-prx4-mqg3
Cilium may not enforce host firewall policies when Native Routing, WireGuard and Node Encryption are enabled
Medium Also affects github.com/cilium/cilium
GHSA-38pp-6gcp-rqvm
Cilium with misconfigured toGroups in policies can lead to unrestricted egress traffic
Medium Also affects github.com/cilium/cilium
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor