CVE-2024-28860: Insecure IPsec transport encryption in Cilium

Published Mar 27, 2024
·
Updated

Impact

Users of IPsec transparent encryption in Cilium may be vulnerable to cryptographic attacks that render the transparent encryption ineffective.

In particular, Cilium is vulnerable to the following attacks by a man-in-the-middle attacker:

- Chosen plaintext attacks - Key recovery attacks - Replay attacks

These attacks are possible due to an ESP sequence number collision when multiple nodes are configured with the same key. Fixed versions of Cilium use unique keys for each IPsec tunnel established between nodes, resolving all of the above attacks.

Important: After upgrading, users must perform a key rotation using the instructions here to ensure that they are no longer vulnerable to this issue. Please note that the key rotation instructions have recently been updated, and users must use the new instructions to properly establish secure IPsec tunnels. To validate that the new instructions have been followed properly, ensure that the IPsec Kubernetes secret contains a "+" sign.

Patches

All prior versions of Cilium that support IPsec transparent encryption (Cilium 1.4 onwards) are affected by this issue.

Patched versions:

- Cilium 1.15.3 - Cilium 1.14.9 - Cilium 1.13.14

Workarounds

There is no workaround to this issue. IPsec transparent encryption users are strongly encouraged to upgrade.

Acknowledgements

The Cilium community has worked together with members of Cure53 and Isovalent to prepare these mitigations. Special thanks to @NikAleksandrov and @pchaigno for their work on remediating the issue. Thanks to Marsh Ray, Senior Software Developer at Microsoft, for input and guidance on the fix.

For more information If you have any questions or comments about this advisory, please reach out on Slack.

As usual, if you think you found a related vulnerability, we strongly encourage you to report security vulnerabilities to our private security mailing list: security@cilium.io - first, before disclosing them in any public forums. This is a private mailing list where only members of the Cilium internal security team are subscribed to, and is treated as top priority.

Other sources

Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Users of IPsec transparent encryption in Cilium may be vulnerable to cryptographic attacks that render the transparent encryption ineffective. In particular, Cilium is vulnerable to chosen plaintext, key recovery, replay attacks by a man-in-the-middle attacker. These attacks are possible due to an ESP sequence number collision when multiple nodes are configured with the same key. Fixed versions of Cilium use unique keys for each IPsec tunnel established between nodes, resolving all of the above attacks. This vulnerability is fixed in 1.13.13, 1.14.9, and 1.15.3.

— MITRE

Affected Software

6 affected componentsFixes available
go/github.com/cilium/cilium>=1.15.0<=1.15.2
1.15.3
go/github.com/cilium/cilium>=1.14.0<=1.14.7
1.14.9
go/github.com/cilium/cilium>=1.4.0<=1.13.13
1.13.14
Cilium Cilium>=1.4.0<1.13.14
Cilium Cilium>=1.14.0<1.14.9
Cilium Cilium>=1.15.0<1.15.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade go/github.com/cilium/cilium to a version that resolves this vulnerability.

    Fixed in 1.15.3
  2. Upgrade

    Upgrade go/github.com/cilium/cilium to a version that resolves this vulnerability.

    Fixed in 1.14.9
  3. Upgrade

    Upgrade go/github.com/cilium/cilium to a version that resolves this vulnerability.

    Fixed in 1.13.14
  4. Upgrade

    Upgrade Cilium to a version that resolves this vulnerability.

    Fixed in 1.13.14
  5. Upgrade

    Upgrade Cilium to a version that resolves this vulnerability.

    Fixed in 1.14.9
  6. Upgrade

    Upgrade Cilium to a version that resolves this vulnerability.

    Fixed in 1.15.3
  7. Operational

    After upgrading, perform IPsec key rotation using the updated key-rotation instructions, and verify that the IPsec Kubernetes secret contains a "+" sign.

Event History

Mar 27, 2024
CVE Published
via MITRE·06:34 PM
Data Sourced
via MITRE·06:34 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:15 PM
RemedyAffected Software
Mar 28, 2024
Advisory Published
via GitHub·05:27 PM
Apr 2, 58713
Event
via FIRST·08:09 AM

Frequently Asked Questions

1

What is the severity of CVE-2024-28860?

CVE-2024-28860 has a high severity due to its potential to allow cryptographic attacks that compromise IPsec transparent encryption in Cilium.

2

How do I fix CVE-2024-28860?

To fix CVE-2024-28860, upgrade to Cilium version 1.15.3, 1.14.9, or 1.13.14 depending on your current version.

3

Which versions of Cilium are affected by CVE-2024-28860?

Cilium versions 1.15.0 to 1.15.2, 1.14.0 to 1.14.7, and 1.4.0 to 1.13.13 are affected by CVE-2024-28860.

4

What kind of attacks does CVE-2024-28860 enable?

CVE-2024-28860 enables cryptographic attacks that can render IPsec transparent encryption ineffective.

5

Is CVE-2024-28860 related to open source software?

Yes, CVE-2024-28860 affects the open source Cilium project, which is used for networking functions in cloud-native environments.

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