github.com/cilium/cilium
Affected
- introduced
0, fixed1.13.13(semver)
Fixed versions
1.13.13
Fix
- Fixed version
1.13.13go get github.com/cilium/[email protected]
Advisory
Also known as: BIT-cilium-2024-28249, BIT-cilium-operator-2024-28249, BIT-cilium-proxy-2024-28249, BIT-hubble-2024-28249, BIT-hubble-relay-2024-28249, BIT-hubble-ui-2024-28249, BIT-hubble-ui-backend-2024-28249, CVE-2024-28249, GO-2024-2656
Unencrypted traffic between nodes when using IPsec and L7 policies
Impact
In Cilium clusters with IPsec enabled and traffic matching Layer 7 policies:
Note: For clusters running in native routing mode, IPsec encryption is not applied to connections which are selected by a L7 Egress Network Policy or a DNS Policy. This is a known limitation of Cilium's IPsec encryption which will continue to apply after upgrading to the latest Cilium versions described below.
Patches
This issue affects:
This issue has been resolved in:
Workarounds
There is no workaround to this issue.
Acknowledgements
The Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to @jschwinger233, @julianwiedmann, @giorio94, and @jrajahalme for their work in triaging and resolving this issue.
For more information
If you have any questions or comments about this advisory, please reach out on Slack.
If you think you have found a vulnerability in Cilium, we strongly encourage you to report it to our private security mailing list at [[email protected]](mailto:[email protected]). This is a private mailing list that only members of the Cilium internal security team are subscribed to, and your report will be treated as top priority.
Medium Basis: The source's own band: MODERATE
0, fixed 1.13.13 (semver)1.13.13
1.13.13go get github.com/cilium/[email protected]1.14.0, fixed 1.14.8 (semver)1.14.8
1.14.8go get github.com/cilium/[email protected]1.15.0, fixed 1.15.2 (semver)1.15.2
1.15.2go get github.com/cilium/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0