CVE-2024-28249: Cilium has possible unencrypted traffic between nodes when using IPsec and L7 policies

Published Mar 18, 2024
·
Updated

Impact

In Cilium clusters with IPsec enabled and traffic matching Layer 7 policies:

- Traffic that should be IPsec-encrypted between a node's Envoy proxy and pods on other nodes is sent unencrypted - Traffic that should be IPsec-encrypted between a node's DNS proxy and pods on other nodes is sent unencrypted

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:

- Cilium v1.15 before v1.15.2 - Cilium v1.14 before v1.14.8 - Cilium v1.13 before v1.13.13 - Cilium v1.4 to v1.12 inclusive

This issue has been resolved in:

- Cilium v1.15.2 - Cilium v1.14.8 - Cilium v1.13.13

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 security@cilium.io. 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.

Other sources

Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Prior to versions 1.13.13, 1.14.8, and 1.15.2, in Cilium clusters with IPsec enabled and traffic matching Layer 7 policies, IPsec-eligible traffic between a node's Envoy proxy and pods on other nodes is sent unencrypted and IPsec-eligible traffic between a node's DNS proxy and pods on other nodes is sent unencrypted. This issue has been resolved in Cilium 1.15.2, 1.14.8, and 1.13.13. There is no known workaround for this issue.

— MITRE

Affected Software

6 affected componentsFixes available
go/github.com/cilium/cilium>=1.15.0<1.15.2
1.15.2
go/github.com/cilium/cilium>=1.14.0<1.14.8
1.14.8
go/github.com/cilium/cilium<1.13.13
1.13.13
Cilium Cilium<1.13.13
Cilium Cilium>=1.14.0<1.14.8
Cilium Cilium>=1.15.0<1.15.2

Event History

Mar 18, 2024
Advisory Published
via GitHub·08:30 PM
CVE Published
via MITRE·09:36 PM
Data Sourced
via MITRE·09:36 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:15 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

What is the severity of CVE-2024-28249?

CVE-2024-28249 is classified as a critical vulnerability due to the risk of unencrypted traffic in Cilium clusters with IPsec enabled.

2

How do I fix CVE-2024-28249?

To fix CVE-2024-28249, upgrade your Cilium installation to version 1.15.2, 1.14.8, or 1.13.13.

3

What versions of Cilium are affected by CVE-2024-28249?

CVE-2024-28249 affects Cilium versions 1.15.0 through 1.15.1, 1.14.0 through 1.14.7, and any version prior to 1.13.13.

4

What are the implications of CVE-2024-28249 for my network security?

CVE-2024-28249 can result in sensitive traffic being transmitted unencrypted, potentially exposing data to interception.

5

Is IPsec support disabled in any affected versions due to CVE-2024-28249?

No, IPsec support is not disabled, but the vulnerability allows specific traffic that should have been encrypted to be sent unencrypted.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203