CVE-2024-28249: Unencrypted traffic between nodes when using IPsec and L7 policies in Cilium
Summary
CVE-2024-28249: Unencrypted traffic between nodes when using IPsec and L7 policies. Affects github.com/cilium/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 · Bitnami
- cilium-operator · Bitnami
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 an open-source project that provides networking and security services for containers and microservices. It utilizes Envoy proxies and IPsec encryption to secure traffic between nodes in a cluster. However, a vulnerability has been identified in Cilium versions before v1.15.2, v1.14.8, and v1.13.13, as well as versions from v1.4 to v1.12. This vulnerability allows unencrypted traffic to be sent 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.
Vulnerability Detail
The vulnerability arises when IPsec encryption is enabled and traffic matches Layer 7 policies. In such cases, the traffic that should be encrypted is sent unencrypted, compromising the security of the communication. This issue affects Cilium clusters running in native routing mode and selecting connections through L7 Egress Network Policies or DNS Policies. The impact of this vulnerability is a potential exposure of sensitive data and unauthorized access to network traffic.
How To Fix
Latest published version: v1.20.3 as of 22 Oct 2026
go get github.com/cilium/cilium@v1.20.3Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
< 1.13.131.13.13go get github.com/cilium/cilium@v1.13.13 -
>= 1.14.0, < 1.14.81.14.8go get github.com/cilium/cilium@v1.14.8 -
>= 1.15.0, < 1.15.21.15.2go get github.com/cilium/cilium@v1.15.2
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
There is no known workaround for this vulnerability. It is essential to upgrade to the patched versions of Cilium to address the issue.
Conclusion
The vulnerability in Cilium versions before v1.15.2, v1.14.8, and v1.13.13, as well as versions from v1.4 to v1.12, allows unencrypted traffic between nodes when using IPsec and L7 policies. This can result in the exposure of sensitive data and unauthorized access to network traffic. To mitigate this risk, it is crucial to upgrade to the latest patched versions of Cilium. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for github.com/cilium/cilium →
FAQ
Cilium is an open-source project that provides networking and security services for containers and microservices. It utilizes Envoy proxies and IPsec encryption to secure traffic between nodes in a cluster.
Cilium versions before v1.15.2, v1.14.8, and v1.13.13, as well as versions from v1.4 to v1.12, are affected by this vulnerability.
The impact of this vulnerability is that traffic that should be encrypted 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, is sent unencrypted. This can lead to the exposure of sensitive data and unauthorized access to network traffic.
To fix this vulnerability, it is recommended to upgrade to the latest versions of Cilium: v1.15.2, v1.14.8, or v1.13.13, depending on the installed version. These versions contain the necessary patches to ensure that traffic is properly encrypted between nodes.
There is no known workaround for this vulnerability. It is essential to upgrade to the patched versions of Cilium to address the issue.
Related vulnerabilities
Recent vulnerabilities recorded for github.com/cilium/cilium.
