Potential HTTP policy bypass when using header rules in Cilium
cve-program · CVE-2023-30851
PublishedCilium 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.
Read the publisher's advisoryeuvd · EUVD-2023-1449
PublishedCilium 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.
Read the publisher's advisorynvd · CVE-2023-30851
PublishedCilium 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.
Read the publisher's advisoryosv · GHSA-2h44-x2wx-49f4
Published### Impact 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. ### Patches This issue has been patched in Cilium 1.11.16, 1.12.9, and 1.13.2. ### Workarounds Rewrite HTTP rules for each endpoint separately. For example, if the initial rule looks like: ``` egress: - toEndpoints: - matchLabels: k8s:kind: echo - matchLabels: k8s:kind: example toPorts: - ports: - port: "8080" protocol: TCP rules: http: - method: "GET" ``` It should be rewritten to: ``` egress: - toEndpoints: - matchLabels: k8s:kind: echo toPorts: - ports: - port: "8080" protocol: TCP rules: http: - method: "GET" - toEndpoints: - matchLabels: k8s:kind: example toPorts: - ports: - port: "8080" protocol: TCP rules: http: - method: "GET" ``` ### Acknowledgements The Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to @jrajahalme for investigating and fixing the issue. ### For more 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). As usual, if you think you found a related vulnerability, we strongly encourage you to report security vulnerabilities to our private security mailing list: [[email protected]](mailto:[email protected]) - first, before disclosing them in any public forums. This is a private mailing list where only members of the Cilium internal security team are subscribed to, and is treated as top priority.
Read the publisher's advisoryosv · GO-2023-1785
PublishedPotential HTTP policy bypass when using header rules in Cilium 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-2023-30851 · CVE overview and exploitation status
BIT-cilium-operator-2023-30851
BIT-hubble-ui-backend-2023-30851
cve-program · CVE-2023-30851
- https://github.com/cilium/cilium/security/advisories/GHSA-2h44-x2wx-49f4
- https://github.com/cilium/cilium/releases/tag/v1.11.16
- https://github.com/cilium/cilium/releases/tag/v1.12.9
- https://github.com/cilium/cilium/releases/tag/v1.13.2
euvd · EUVD-2023-1449
- https://github.com/cilium/cilium/security/advisories/GHSA-2h44-x2wx-49f4
- https://github.com/cilium/cilium/releases/tag/v1.11.16
- https://github.com/cilium/cilium/releases/tag/v1.12.9
- https://github.com/cilium/cilium/releases/tag/v1.13.2
nvd · CVE-2023-30851
- https://github.com/cilium/cilium/releases/tag/v1.11.16
- https://github.com/cilium/cilium/releases/tag/v1.12.9
- https://github.com/cilium/cilium/releases/tag/v1.13.2
- https://github.com/cilium/cilium/security/advisories/GHSA-2h44-x2wx-49f4
osv · GHSA-2h44-x2wx-49f4
- https://github.com/cilium/cilium/security/advisories/GHSA-2h44-x2wx-49f4
- https://nvd.nist.gov/vuln/detail/CVE-2023-30851
- https://github.com/cilium/cilium
- https://github.com/cilium/cilium/releases/tag/v1.11.16
- https://github.com/cilium/cilium/releases/tag/v1.12.9
- https://github.com/cilium/cilium/releases/tag/v1.13.2
osv · GO-2023-1785
Related changes
Linked by CVE identifierNo related changes are available here.