Cilium has possible unencrypted traffic between nodes when using IPsec and L7 policies
- 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.13.13, 1.14.8, 1.15.2
- 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.13.13, 1.14.8, and 1.15.2, in Cilium clusters with IPsec enabled and traffic matching Layer 7 policies, IPsec-eligible traffic between a node's Envoy proxy and pods on other nodes is sent unencrypted and IPsec-eligible traffic between a node's DNS proxy and pods on other nodes is sent unencrypted. This issue has been resolved in Cilium 1.15.2, 1.14.8, and 1.13.13. There is no known workaround for this issue.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- cilium cilium
fixed in 1.13.13; From 1.14.0 · fixed in 1.14.8; From 1.15.0 · fixed in 1.15.2
- github.com/cilium/ciliumGo
fixed in 1.13.13
- github.com/cilium/ciliumGo
From 1.14.0 · fixed in 1.14.8
- github.com/cilium/ciliumGo
From 1.15.0 · fixed in 1.15.2
- github.com/cilium/ciliumGo
fixed in 1.13.13; From 1.14.0 · fixed in 1.14.8; From 1.15.0 · fixed in 1.15.2