CVE-2024-25630: Cilium has unencrypted ingress/health traffic when using Wireguard transparent encryption

Published Feb 20, 2024
·
Updated

Impact

For Cilium users who are using CRDs to store Cilium state (the default configuration) and Wireguard transparent encryption, responses from pods to the Ingress and health endpoints are not encrypted. Traffic from the Ingress and health endpoints to pods is not affected by this issue. The health endpoint is only used for Cilium's internal health checks.

Patches

This issue affects Cilium v1.14 before v1.14.7.

This issue has been patched in Cilium v1.14.7.

Workarounds

There is no workaround to this issue - affected users are encouraged to upgrade.

Acknowledgements

The Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to @gandro for their work on triaging and remediating 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 affecting Cilium, we strongly encourage you to report it to our security mailing list at security@cilium.io. This is a private mailing list where 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. For Cilium users who are using CRDs to store Cilium state (the default configuration) and Wireguard transparent encryption, traffic to/from the Ingress and health endpoints is not encrypted. This issue affects Cilium v1.14 before v1.14.7 and has been patched in Cilium v1.14.7. There is no workaround to this issue.

— MITRE

Affected Software

2 affected componentsFixes available
go/github.com/cilium/cilium>=1.14.0<1.14.7
1.14.7
Cilium Cilium>=1.14.0<1.14.7

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.14.7
  2. Upgrade

    Upgrade Cilium to a version that resolves this vulnerability.

    Fixed in v1.14.7

Event History

Feb 20, 2024
CVE Published
via MITRE·05:53 PM
Data Sourced
via MITRE·05:53 PM
DescriptionSeverityWeakness
Advisory Published
via GitHub·11:44 PM

Frequently Asked Questions

1

What is the severity of CVE-2024-25630?

CVE-2024-25630 has been classified with a severity that affects Cilium's CRDs when utilizing Wireguard for encryption.

2

How do I fix CVE-2024-25630?

To remediate CVE-2024-25630, upgrade Cilium to version 1.14.7 or later.

3

Which software versions are affected by CVE-2024-25630?

CVE-2024-25630 affects Cilium versions between 1.14.0 and 1.14.7.

4

What impact does CVE-2024-25630 have on Cilium users?

CVE-2024-25630 can cause unexpected responses from pods to the Ingress and health endpoints under certain configurations.

5

Is Wireguard impacted by CVE-2024-25630?

Yes, CVE-2024-25630 impacts users of Wireguard transparent encryption when using Cilium's CRDs.

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