CVE-2024-42488: Cilium agent's race condition may lead to policy bypass for Host Firewall policy

Published Aug 15, 2024
·
Updated

Impact

A race condition in the Cilium agent can cause the agent to ignore labels that should be applied to a node. This could in turn cause CiliumClusterwideNetworkPolicies intended for nodes with the ignored label to not apply, leading to policy bypass.

Patches

This issue was fixed in https://github.com/cilium/cilium/pull/33511.

This issue affects:

- All versions of Cilium before v1.14.14 - Cilium v1.15 between v1.15.0 and v1.15.7 inclusive

This issue has been patched in:

- Cilium v1.14.14 - Cilium v1.15.8

Workarounds

As the underlying issue depends on a race condition, users unable to upgrade can restart the Cilium agent on affected nodes until the affected policies are confirmed to be working as expected.

Acknowledgements

The Cilium community has worked together with members of Google and Isovalent to prepare these mitigations. Special thanks to @skmatti for raising 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 affecting Cilium, we strongly encourage you to report it to our security mailing list at security@cilium.io. This is a private mailing list for the Cilium security team, 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.14.14 and 1.15.8, a race condition in the Cilium agent can cause the agent to ignore labels that should be applied to a node. This could in turn cause CiliumClusterwideNetworkPolicies intended for nodes with the ignored label to not apply, leading to policy bypass. This issue has been patched in Cilium v1.14.14 and v1.15.8 As the underlying issue depends on a race condition, users unable to upgrade can restart the Cilium agent on affected nodes until the affected policies are confirmed to be working as expected.

— MITRE

Affected Software

4 affected componentsFixes available
go/github.com/cilium/cilium>=1.15.0<1.15.8
1.15.8
go/github.com/cilium/cilium<1.14.14
1.14.14
Cilium Cilium<1.14.14
Cilium Cilium>=1.15.0<1.15.8

Event History

Aug 15, 2024
CVE Published
via MITRE·08:36 PM
Data Sourced
via MITRE·08:36 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:15 PM
DescriptionSeverityWeakness
Advisory Published
via GitHub·09:43 PM

Frequently Asked Questions

1

What is the severity of CVE-2024-42488?

CVE-2024-42488 has a critical severity level due to the potential policy bypass caused by the race condition.

2

How do I fix CVE-2024-42488?

To remediate CVE-2024-42488, upgrade the Cilium package to version 1.15.8 or 1.14.14.

3

What type of vulnerability is CVE-2024-42488?

CVE-2024-42488 is classified as a race condition vulnerability affecting the Cilium agent.

4

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

CVE-2024-42488 affects Cilium versions from 1.15.0 to below 1.15.8 and up to 1.14.14.

5

What could be the impact of CVE-2024-42488 in my environment?

The impact of CVE-2024-42488 could lead to unintended policy bypass for CiliumClusterwideNetworkPolicies.

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