Cilium with misconfigured toGroups in policies can lead to unrestricted egress 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.16.17, 1.17.10, 1.18.4
- 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.16.17, 1.17.10, and 1.18.4, CiliumNetworkPolicys which use egress.toGroups.aws.securityGroupsIds to reference AWS security group IDs that do not exist or are not attached to any network interface may unintentionally allow broader outbound access than intended by the policy authors. In such cases, the toCIDRset section of the derived policy is not generated, which means outbound traffic may be permitted to more destinations than originally intended. This issue has been patched in versions 1.16.17, 1.17.10, and 1.18.4. There are no workarounds 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.16.17; From 1.17.0 · fixed in 1.17.10; From 1.18.0 · fixed in 1.18.4
- github.com/cilium/ciliumGo
fixed in 1.16.17; From 1.17.0 · fixed in 1.17.10; From 1.18.0 · fixed in 1.18.4
- github.com/cilium/ciliumGo
From 1.18.0 · fixed in 1.18.4
- github.com/cilium/ciliumGo
From 1.17.0 · fixed in 1.17.10
- github.com/cilium/ciliumGo
fixed in 1.16.17