Cilium vulnerable to potential network policy bypass when routing IPv6 traffic
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.11.15, 1.12.8, 1.13.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Prior to versions 1.11.15, 1.12.8, and 1.13.1, under specific conditions, Cilium may misattribute the source IP address of traffic to a cluster, identifying external traffic as coming from the host on which Cilium is running. As a consequence, network policies for that cluster might be bypassed, depending on the specific network policies enabled. This issue only manifests when Cilium is routing IPv6 traffic and NodePorts are used to route traffic to pods. IPv6 and endpoint routes are both disabled by default. The problem has been fixed and is available on versions 1.11.15, 1.12.8, and 1.13.1. As a workaround, disable IPv6 routing.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- cilium cilium
fixed in 1.11.15; From 1.12.0 · fixed in 1.12.8; From 1.13.0 · fixed in 1.13.1
- github.com/cilium/ciliumGo
fixed in 1.11.15
- github.com/cilium/ciliumGo
From 1.12.0 · fixed in 1.12.8
- github.com/cilium/ciliumGo
From 1.13.0 · fixed in 1.13.1
- github.com/cilium/ciliumGo
fixed in 1.11.15; From 1.12.0 · fixed in 1.12.8; From 1.13.0 · fixed in 1.13.1