CVE-2024-42487
published 2024-08-15CVE-2024-42487: Cilium 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…
PriorityP423medium4.3CVSS 3.1
AVNACLPRLUINSUCLINAN
EPSS
0.53%
43.9th percentile
Cilium 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.
Affected
6 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| cilium | cilium | — | — |
| cilium | cilium | — | — |
| cilium | cilium | — | — |
| cilium | cilium | >= 1.15.0 < 1.15.8 | 1.15.8 |
| github.com | cilium_cilium | >= 1.15.0 < 1.15.8 | 1.15.8 |
| github.com | cilium_cilium | >= 1.16.0 < 1.16.1 | 1.16.1 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
Gateway API route matching order contradicts specification in github.com/cilium/cilium
osv·2024-08-16
CVE-2024-42487 Gateway API route matching order contradicts specification in github.com/cilium/cilium
Gateway API route matching order contradicts specification in github.com/cilium/cilium
Gateway API route matching order contradicts specification in github.com/cilium/cilium
GHSA
Gateway API route matching order contradicts specification
ghsa·2024-08-15
CVE-2024-42487 [MEDIUM] CWE-113 Gateway API route matching order contradicts specification
Gateway API route matching order contradicts specification
### 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
OSV
Gateway API route matching order contradicts specification
osv·2024-08-15
CVE-2024-42487 [MEDIUM] Gateway API route matching order contradicts specification
Gateway API route matching order contradicts specification
### 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
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2024-08-15
Published