Cilium packets from terminating endpoints may not be encrypted in Wireguard-enabled clusters
- 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 v1.15.16, v1.16.9, v1.17.3, 1.15.16, 1.16.9, and 1 more
- 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. Versions 1.15.0 to 1.15.15, 1.16.0 to 1.16.8, and 1.17.0 to 1.17.2, are vulnerable when using Wireguard transparent encryption in a Cilium cluster, packets that originate from a terminating endpoint can leave the source node without encryption due to a race condition in how traffic is processed by Cilium. This issue has been patched in versions 1.15.16, 1.16.9, and 1.17.3. There are no workarounds available for this issue.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- cilium cilium
From v1.13.0 · fixed in v1.15.16; From v1.16.0 · fixed in v1.16.9; From v1.17.0 · fixed in v1.17.3
- github.com/cilium/ciliumGo
From 1.13.0 · fixed in 1.15.16; From 1.16.0 · fixed in 1.16.9; From 1.17.0 · fixed in 1.17.3
- github.com/cilium/ciliumGo
From 1.13.0 · fixed in 1.15.16
- github.com/cilium/ciliumGo
From 1.16.0 · fixed in 1.16.9
- github.com/cilium/ciliumGo
From 1.17.0 · fixed in 1.17.3