Cilium has an information leakage via insecure default Hubble UI CORS header
ImpactFor users who deploy Hubble UI using either Cilium CLI or via the Cilium Helm chart, an insecure default `Access-Control-Allow-Origin` header value could lead to sensitive data exposure. A user with access to a Hubble UI instance affected by this issue could leak configuration details about the Kubernetes cluster which Hubble UI is monitoring, including node names, IP addresses, and other metadata about workloads and the cluster networking configuration. In order for this vulnerability to be exploited, a victim would have to first visit a malicious page.PatchesThis issue was patched in https://github.com/cilium/cilium/commit/a3489f190ba6e87b5336ee685fb6c80b1270d06dThis issue affects:Cilium between v1.14.0 and v1.14.18 inclusiveCilium between v1.15.0 and v1.15.12 inclusiveCilium between v1.16.0 and v1.16.5 inclusiveThis issue is patched in:Cilium v1.14.19Cilium v1.15.13Cilium v1.16.6WorkaroundsUsers who deploy Hubble UI using the Cilium Helm chart directly can remove the CORS headers from the Helm template as shown in the [patch](https://github.com/cilium/cilium/commit/a3489f190ba6e87b5336ee685fb6c80b1270d06d).AcknowledgementsThe Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to @ciffelia for reporting this issue and to @geakstr for the fix.For more informationIf 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 [security@cilium.io](mailto:security@cilium.io). This is a private mailing list for the Cilium security team, and your report will be treated as top priority.