Potential HTTP policy bypass when using header rules in Cilium
Cilium is a networking, observability, and security solution with an eBPF-based dataplane. This issue only impacts users who have a HTTP policy that applies to multiple `toEndpoints` AND have an allow-all rule in place that affects only one of those endpoints. In such cases, a wildcard rule will be appended to the set of HTTP rules, which could cause bypass of HTTP policies. This issue has been patched in Cilium 1.11.16, 1.12.9, and 1.13.2.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2023-30851US | medium5.3 | — | ||
Cilium is a networking, observability, and security solution with an eBPF-based dataplane. This issue only impacts users who have a HTTP policy that applies to multiple `toEndpoint… | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/cilium/cilium/releases/tag/v1.11.16ARTICLE
- https://github.com/cilium/cilium/releases/tag/v1.12.9ARTICLE
- https://github.com/cilium/cilium/releases/tag/v1.13.2ARTICLE
- https://github.com/cilium/cilium/security/advisories/GHSA-2h44-x2wx-49f4ADVISORY
- https://nvd.nist.gov/vuln/detail/CVE-2023-30851WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan