CVE-2024-28250

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 @brb, @giorio94, @gandro and @jschwinger233 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 found a related vulnerability, we strongly encourage you to report security vulnerabilities to our private security mailing list at [email protected]. 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.

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

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

CVE-2024-28250 has a CVSS score of 6.1 (Medium). The vector is reachable from an adjacent network, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.14.8, 1.15.2); upgrading removes the vulnerable code path.

Kodem intelligence

This issue affects:

• In native routing mode (routingMode=native):
  • Cilium v1.14 versions before v1.14.8
  • Cilium v1.15 versions before v1.15.2
• In tunneling mode (routingMode=tunnel):
  • Cilium v1.14 versions before v1.14.4
  • Cilium v1.14.4 if encryption.wireguard.encapsulate is set to false (default).

This issue has been resolved in:

• In native routing mode (routingMode=native):
  • Cilium v1.14.8
  • Cilium v1.15.2
• In tunneling mode (routingMode=tunnel):
  • Cilium v1.14.4. NOTE encryption.wireguard.encapsulate must be set to true.

1. What is CVE-2024-28250? CVE-2024-28250 is a medium-severity security vulnerability in github.com/cilium/cilium (go), affecting versions >= 1.14.0, < 1.14.8. It is fixed in 1.14.8, 1.15.2.
2. How severe is CVE-2024-28250? CVE-2024-28250 has a CVSS score of 6.1 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/cilium/cilium are affected by CVE-2024-28250? github.com/cilium/cilium (go) versions >= 1.14.0, < 1.14.8 is affected.
4. Is there a fix for CVE-2024-28250? Yes. CVE-2024-28250 is fixed in 1.14.8, 1.15.2. Upgrade to this version or later.
5. Is CVE-2024-28250 exploitable, and should I be worried? Whether CVE-2024-28250 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2024-28250 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2024-28250?
   • Upgrade github.com/cilium/cilium to 1.14.8 or later
   • Upgrade github.com/cilium/cilium to 1.15.2 or later