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.
The product receives data from an HTTP agent/component (e.g., web server, proxy, browser, etc.), but it does not neutralize or incorrectly neutralizes CR and LF characters before the data is included in outgoing HTTP headers.
Product A handles inputs or steps differently than Product B, which causes A to perform incorrect actions based on its perception of B's state.
| Link | Tags |
|---|---|
| https://github.com/cilium/cilium/security/advisories/GHSA-qcm3-7879-xcww | vendor advisory |
| https://github.com/cilium/cilium/pull/34109 | third party advisory patch |
| https://github.com/cilium/cilium/commit/a3510fe4a92305822aa1a5e08cb6d6c873c8699a | third party advisory patch |