Cilium with misconfigured toGroups in policies can lead to unrestricted egress traffic
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 4epss 0.2%
exploitation probability
0.2%top 93% of all CVEs
observed exploitation
nono source reports it
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.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Affected products
cilium · ciliumReferences
https://github.com/cilium/cilium/commit/a385856b59c8289cc7273fa3a3062bbf0ef96c97https://github.com/cilium/cilium/releases/tag/v1.16.17https://github.com/cilium/cilium/releases/tag/v1.17.10https://github.com/cilium/cilium/releases/tag/v1.18.4https://github.com/cilium/cilium/security/advisories/GHSA-38pp-6gcp-rqvm