Unencrypted IPsec-Eligible Traffic in Cilium
Summary
CVE-2024-28249: Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Affects cilium across 3 version ranges.
< 1.13.13
>= 1.14.0, < 1.14.8
>= 1.15.0, < 1.15.2
Fixed in 1.13.13, 1.14.8 or 1.15.2, depending on the release line you run. How to fix ↓
Also tracked for
- hubble-ui · Bitnami
- hubble-ui-backend · Bitnami
- cilium-proxy · Bitnami
- hubble · Bitnami
- hubble-relay · Bitnami
- cilium-operator · Bitnami
- github.com/cilium/cilium · Go
- github.com/cilium/cilium · Go
The same CVE-2024-28249 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Cilium is a networking, observability, and security solution that utilizes an eBPF-based dataplane. It is designed to enhance network connectivity, monitoring, and protection in Kubernetes clusters. Cilium leverages IPsec to secure network traffic between nodes and enforce Layer 7 policies. However, prior to versions 1.13.13, 1.14.8, and 1.15.2, there was a vulnerability in Cilium clusters with IPsec enabled. This vulnerability allowed IPsec-eligible traffic between a node's Envoy proxy and pods on other nodes, as well as between a node's DNS proxy and pods on other nodes, to be sent unencrypted.
Vulnerability Detail
The vulnerability in Cilium clusters with IPsec enabled and traffic matching Layer 7 policies allowed IPsec-eligible traffic between a node's Envoy proxy and pods on other nodes, as well as between a node's DNS proxy and pods on other nodes, to be sent unencrypted. This means that sensitive data transmitted over these connections could be intercepted and compromised. The issue has been resolved in Cilium versions 1.13.13, 1.14.8, and 1.15.2.
How To Fix
Fixed versions by release line
The minimum fixed version depends on the release line you run.
-
< 1.13.131.13.13 -
>= 1.14.0, < 1.14.81.14.8 -
>= 1.15.0, < 1.15.21.15.2
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Conclusion
The vulnerability in Cilium clusters with IPsec enabled and traffic matching Layer 7 policies allowed unencrypted IPsec-eligible traffic between a node's Envoy proxy and pods on other nodes, as well as between a node's DNS proxy and pods on other nodes. This could lead to the interception and compromise of sensitive data. It is crucial to upgrade to Cilium versions 1.13.13, 1.14.8, or 1.15.2 to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for cilium →
FAQ
This vulnerability allows unencrypted IPsec-eligible traffic between a node's Envoy proxy and pods on other nodes, as well as between a node's DNS proxy and pods on other nodes. It puts sensitive data transmitted over these connections at risk of interception and compromise.
Yes, all Cilium clusters with IPsec enabled and traffic matching Layer 7 policies are affected by this vulnerability prior to versions 1.13.13, 1.14.8, and 1.15.2.
You can check the version of Cilium installed in your cluster by running the following command: cilium version.
No, there is no known workaround for this vulnerability. It is recommended to upgrade to the fixed versions of Cilium.
You can find more information about this vulnerability in the Cilium GitHub repository: https://github.com/bitnami/vulndb/tree/main/data/cilium/BIT-cilium-2024-28249.json.
References
Related vulnerabilities
Recent vulnerabilities recorded for cilium.
