Advisory

GHSA-wc5v-r48v-g4vh

Also known as: None

Summary

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

Details

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: [[email protected]](mailto:[email protected])—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.

Severity

Low Basis: The source's own band: LOW

Dates

Published
2022-07-15 21:46 UTC
Modified
2026-09-10 03:49 UTC

Affected packages and fixes

github.com/cilium/cilium

Go · All systems

Affected

  • introduced 0, fixed 1.10.13 (semver)

Fixed versions

1.10.13

Fix

github.com/cilium/cilium

Go · All systems

Affected

  • introduced 1.11.0, fixed 1.11.7 (semver)

Fixed versions

1.11.7

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences