Cilium's Gateway API route matching order contradicts specification
cve-program · CVE-2024-42487
PublishedCilium is a networking, observability, and security solution with an eBPF-based dataplane. In the 1.15 branch prior to 1.15.8 and the 1.16 branch prior to 1.16.1, 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. This could result in unexpected behaviour with security This issue is fixed in Cilium v1.15.8 and v1.16.1. There is no workaround for this issue.
Read the publisher's advisoryeuvd · EUVD-2024-2632
PublishedCilium is a networking, observability, and security solution with an eBPF-based dataplane. In the 1.15 branch prior to 1.15.8 and the 1.16 branch prior to 1.16.1, 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. This could result in unexpected behaviour with security This issue is fixed in Cilium v1.15.8 and v1.16.1. There is no workaround for this issue.
Read the publisher's advisorynvd · CVE-2024-42487
PublishedCilium is a networking, observability, and security solution with an eBPF-based dataplane. In the 1.15 branch prior to 1.15.8 and the 1.16 branch prior to 1.16.1, 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. This could result in unexpected behaviour with security This issue is fixed in Cilium v1.15.8 and v1.16.1. There is no workaround for this issue.
Read the publisher's advisoryosv · GHSA-qcm3-7879-xcww
Published### Impact 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](https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPRouteRule), [GRPCRouteRule](https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io%2fv1.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. ### Patches 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 ### 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](https://docs.cilium.io/en/latest/community/community/#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]](mailto:[email protected]). This is a private mailing list for the Cilium security team, and your report will be treated as top priority.
Read the publisher's advisoryosv · GO-2024-3071
PublishedGateway API route matching order contradicts specification in github.com/cilium/cilium
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2024-42487 · CVE overview and exploitation status
BIT-cilium-operator-2024-42487
cve-program · CVE-2024-42487
- https://github.com/cilium/cilium/security/advisories/GHSA-qcm3-7879-xcww
- https://github.com/cilium/cilium/pull/34109
- https://github.com/cilium/cilium/commit/a3510fe4a92305822aa1a5e08cb6d6c873c8699a
euvd · EUVD-2024-2632
- https://github.com/cilium/cilium/security/advisories/GHSA-qcm3-7879-xcww
- https://github.com/cilium/cilium/pull/34109
- https://github.com/cilium/cilium/commit/a3510fe4a92305822aa1a5e08cb6d6c873c8699a
nvd · CVE-2024-42487
- https://github.com/cilium/cilium/commit/a3510fe4a92305822aa1a5e08cb6d6c873c8699a
- https://github.com/cilium/cilium/pull/34109
- https://github.com/cilium/cilium/security/advisories/GHSA-qcm3-7879-xcww
osv · GHSA-qcm3-7879-xcww
- https://github.com/cilium/cilium/security/advisories/GHSA-qcm3-7879-xcww
- https://nvd.nist.gov/vuln/detail/CVE-2024-42487
- https://github.com/cilium/cilium/pull/34109
- https://github.com/cilium/cilium/commit/a3510fe4a92305822aa1a5e08cb6d6c873c8699a
- https://github.com/cilium/cilium/commit/d88772b9c29e370becbc4547cada6711d51edcde
- https://github.com/cilium/cilium/commit/fe42273566a943a0f3174c87b23a195c856b51d6
- https://github.com/cilium/cilium
osv · GO-2024-3071
- https://github.com/cilium/cilium/security/advisories/GHSA-qcm3-7879-xcww
- https://nvd.nist.gov/vuln/detail/CVE-2024-42487
- https://github.com/cilium/cilium/commit/a3510fe4a92305822aa1a5e08cb6d6c873c8699a
- https://github.com/cilium/cilium/commit/d88772b9c29e370becbc4547cada6711d51edcde
- https://github.com/cilium/cilium/commit/fe42273566a943a0f3174c87b23a195c856b51d6
- https://github.com/cilium/cilium/pull/34109
Related changes
Linked by CVE identifier- Release 2025-01-30 · Tool release · 14 Feb 2025