CVE-2024-42487

Workarounds

There is no workaround for this issue.

Acknowledgements

The Cilium community has worked together with members of Cure53 and Isovalent to prepare these mitigations. Special thanks to @sayboras for remediating this issue.

Further 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 [email protected]. This is a private mailing list for the Cilium security team, and your report will be treated as top priority.

Gateway API HTTPRoutes and GRPCRoutes do not follow the match precedence specified in the Gateway API specification. In particular, request headers are matched before request methods, when the specification describes that the request methods must be respected before headers are matched (HTTPRouteRule, GRPCRouteRule).

If users create Gateway API resources that use both request headers and request methods in order to route to different destinations, then traffic may be delivered to the incorrect backend. If the backend does not have Network Policy restricting acceptable traffic to receive, then requests may access information that you did not intend for them to access.

CVE-2024-42487 has a CVSS score of 4.0 (Medium). The vector is network-reachable, 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.16.1, 1.15.8); upgrading removes the vulnerable code path.

Kodem intelligence

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

This issue affects:

• Cilium v1.15 between v1.15.0 and v1.15.7 inclusive
• Cilium v1.16.0

This issue is fixed in:

• Cilium v1.15.8
• Cilium v1.16.1

1. What is CVE-2024-42487? CVE-2024-42487 is a medium-severity security vulnerability in github.com/cilium/cilium (go), affecting versions = 1.16.0. It is fixed in 1.16.1, 1.15.8.
2. How severe is CVE-2024-42487? CVE-2024-42487 has a CVSS score of 4.0 (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-42487? github.com/cilium/cilium (go) versions = 1.16.0 is affected.
4. Is there a fix for CVE-2024-42487? Yes. CVE-2024-42487 is fixed in 1.16.1, 1.15.8. Upgrade to this version or later.
5. Is CVE-2024-42487 exploitable, and should I be worried? Whether CVE-2024-42487 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-42487 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-42487?
   • Upgrade github.com/cilium/cilium to 1.16.1 or later
   • Upgrade github.com/cilium/cilium to 1.15.8 or later