{"id":"CVE-2023-34242","aliases":["BIT-cilium-2023-34242","BIT-cilium-operator-2023-34242","BIT-cilium-proxy-2023-34242","BIT-hubble-2023-34242","BIT-hubble-relay-2023-34242","BIT-hubble-ui-2023-34242","BIT-hubble-ui-backend-2023-34242","EUVD-2023-1875","GHSA-r7wr-4w5q-55m6","GO-2023-1862"],"status":"published","title":"Cilium vulnerable to information leakage via incorrect ReferenceGrant handling","description":"Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Prior to version 1.13.4, when Gateway API is enabled in Cilium, the absence of a check on the namespace in which a ReferenceGrant is created could result in Cilium unintentionally gaining visibility of secrets (including certificates) and services across namespaces. An attacker on an affected cluster can leverage this issue to use cluster secrets that should not be visible to them, or communicate with services that they should not have access to. Gateway API functionality is disabled by default. This vulnerability is fixed in Cilium release 1.13.4. As a workaround, restrict the creation of `ReferenceGrant` resources to admin users by using Kubernetes RBAC.","severity":{"version":"3.1","score":3.4,"vector":"CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N","level":"low","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-11","score":0.00305,"percentile":0.23581,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-200"],"published":"2023-06-15T19:07:14Z","modified":"2026-10-28T02:30:57Z","fixes":[{"ecosystem":"Go","package":"github.com/cilium/cilium","fixed_in":["1.13.4"],"sources":["ghsa","osv"]},{"ecosystem":"Bitnami","package":"cilium","fixed_in":["1.13.4"],"sources":["osv"]},{"ecosystem":"Bitnami","package":"cilium-operator","fixed_in":["1.13.4"],"sources":["osv"]},{"ecosystem":"Bitnami","package":"cilium-proxy","fixed_in":["1.13.4"],"sources":["osv"]},{"ecosystem":"Bitnami","package":"hubble","fixed_in":["1.13.4"],"sources":["osv"]},{"ecosystem":"Bitnami","package":"hubble-relay","fixed_in":["1.13.4"],"sources":["osv"]},{"ecosystem":"Bitnami","package":"hubble-ui","fixed_in":["1.13.4"],"sources":["osv"]},{"ecosystem":"Bitnami","package":"hubble-ui-backend","fixed_in":["1.13.4"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"Go","package":"github.com/cilium/cilium","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.13.0"},{"fixed":"1.13.4"}]}]},{"source":"osv","ecosystem":"Bitnami","package":"cilium","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.13.4"}]}]},{"source":"osv","ecosystem":"Bitnami","package":"cilium-operator","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.13.4"}]}]},{"source":"osv","ecosystem":"Bitnami","package":"cilium-proxy","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.13.4"}]}]},{"source":"osv","ecosystem":"Bitnami","package":"hubble","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.13.4"}]}]},{"source":"osv","ecosystem":"Bitnami","package":"hubble-relay","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.13.4"}]}]},{"source":"osv","ecosystem":"Bitnami","package":"hubble-ui","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.13.4"}]}]},{"source":"osv","ecosystem":"Bitnami","package":"hubble-ui-backend","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.13.4"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/cilium/cilium","ranges":[{"type":"SEMVER","events":[{"introduced":"1.13.0"},{"fixed":"1.13.4"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/cilium/cilium","ranges":[{"type":"SEMVER","events":[{"introduced":"1.13.0"},{"fixed":"1.13.4"}]}]}],"products":[{"vendor":"cilium","product":"cilium"}],"references":[{"url":"https://github.com/cilium/cilium/security/advisories/GHSA-r7wr-4w5q-55m6","tags":["x_refsource_CONFIRM","x_transferred","Third Party Advisory","advisory","web"]},{"url":"https://github.com/cilium/cilium/releases/tag/v1.13.4","tags":["x_refsource_MISC","x_transferred","Release Notes","article","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-34242","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-r7wr-4w5q-55m6"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/34xxx/CVE-2023-34242.json","tags":["advisory"]},{"url":"https://github.com/cilium/cilium","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2023-34242","title":"Cilium vulnerable to information leakage via incorrect ReferenceGrant handling","description":"Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Prior to version 1.13.4, when Gateway API is enabled in Cilium, the absence of a check on the namespace in which a ReferenceGrant is created could result in Cilium unintentionally gaining visibility of secrets (including certificates) and services across namespaces. An attacker on an affected cluster can leverage this issue to use cluster secrets that should not be visible to them, or communicate with services that they should not have access to. Gateway API functionality is disabled by default. This vulnerability is fixed in Cilium release 1.13.4. As a workaround, restrict the creation of `ReferenceGrant` resources to admin users by using Kubernetes RBAC.","status":"published","published":"2023-06-15T19:07:14.624Z","modified":"2024-12-11T21:11:29.299Z","cvss":[{"version":"3.1","score":3.4,"vector":"CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N","level":"low","assessor":"cna"}],"cwes":["CWE-200"],"updated_at":"2026-11-02T14:35:35.912488Z"}],"euvd":[{"id":"EUVD-2023-1875","description":"Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Prior to version 1.13.4, when Gateway API is enabled in Cilium, the absence of a check on the namespace in which a ReferenceGrant is created could result in Cilium unintentionally gaining visibility of secrets (including certificates) and services across namespaces. An attacker on an affected cluster can leverage this issue to use cluster secrets that should not be visible to them, or communicate with services that they should not have access to. Gateway API functionality is disabled by default. This vulnerability is fixed in Cilium release 1.13.4. As a workaround, restrict the creation of `ReferenceGrant` resources to admin users by using Kubernetes RBAC.","status":"published","published":"2023-06-15T19:07:14Z","modified":"2024-12-11T21:11:29Z","cvss":[{"version":"3.1","score":3.4,"vector":"CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N","level":"low"}],"updated_at":"2026-11-03T00:04:36.46341Z"}],"ghsa":[{"id":"GHSA-r7wr-4w5q-55m6","title":"Cilium vulnerable to information leakage via incorrect ReferenceGrant handling","description":"### Impact\n\nWhen the [Gateway API](https://docs.cilium.io/en/v1.13/network/servicemesh/gateway-api/gateway-api/) is enabled in Cilium, the absence of a check on the namespace in which a [ReferenceGrant](https://gateway-api.sigs.k8s.io/api-types/referencegrant/) is created could result in Cilium gaining visibility of secrets (including certificates) and services across namespaces.\n\nAn attacker on an affected cluster can configure Cilium to use cluster secrets or communicate with services that it should not have access to.\n\nGateway API functionality is disabled by default.\n\n### Patches\n\nThis vulnerability is fixed in Cilium release 1.13.4.\n\nCilium versions \u003c1.13 are not affected.\n\n### Workarounds\n\nThere is no workaround to this issue.\n\n### Acknowledgements\nThe Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to @meyskens for investigating and fixing the issue.\n\n### For more information\nIf you have any questions or comments about this advisory, please reach out on [Slack](https://docs.cilium.io/en/latest/community/community/#slack).\n\nAs usual, if you think you found a related vulnerability, we strongly encourage you to report security vulnerabilities to our private security mailing list: [security@cilium.io](mailto:security@cilium.io) - 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.\n","status":"published","published":"2023-06-16T17:47:56Z","modified":"2023-11-08T05:03:43Z","cvss":[{"version":"3.1","score":3.4,"vector":"CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N","level":"low"}],"cwes":["CWE-200"],"updated_at":"2026-11-02T14:37:16.721714Z"}],"nvd":[{"id":"CVE-2023-34242","description":"Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Prior to version 1.13.4, when Gateway API is enabled in Cilium, the absence of a check on the namespace in which a ReferenceGrant is created could result in Cilium unintentionally gaining visibility of secrets (including certificates) and services across namespaces. An attacker on an affected cluster can leverage this issue to use cluster secrets that should not be visible to them, or communicate with services that they should not have access to. Gateway API functionality is disabled by default. This vulnerability is fixed in Cilium release 1.13.4. As a workaround, restrict the creation of `ReferenceGrant` resources to admin users by using Kubernetes RBAC.","status":"published","published":"2023-06-15T20:15:09.473Z","modified":"2026-06-17T06:03:12.363Z","cvss":[{"version":"3.1","score":3.4,"vector":"CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N","level":"low","assessor":"secondary"},{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","level":"medium","assessor":"primary"}],"cwes":["CWE-200"],"updated_at":"2026-11-02T14:08:06.335469Z"}],"osv":[{"id":"CVE-2023-34242","title":"Cilium vulnerable to information leakage via incorrect ReferenceGrant handling","description":"Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Prior to version 1.13.4, when Gateway API is enabled in Cilium, the absence of a check on the namespace in which a ReferenceGrant is created could result in Cilium unintentionally gaining visibility of secrets (including certificates) and services across namespaces. An attacker on an affected cluster can leverage this issue to use cluster secrets that should not be visible to them, or communicate with services that they should not have access to. Gateway API functionality is disabled by default. This vulnerability is fixed in Cilium release 1.13.4. As a workaround, restrict the creation of `ReferenceGrant` resources to admin users by using Kubernetes RBAC.","status":"published","published":"2023-06-15T19:07:14.624Z","modified":"2026-10-28T02:30:57.19589764Z","cvss":[{"version":"3.1","score":3.4,"vector":"CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N","level":"low"}],"cwes":["CWE-200"],"updated_at":"2026-11-02T15:44:32.116263Z"},{"id":"GHSA-r7wr-4w5q-55m6","title":"Cilium vulnerable to information leakage via incorrect ReferenceGrant handling","description":"### Impact\n\nWhen the [Gateway API](https://docs.cilium.io/en/v1.13/network/servicemesh/gateway-api/gateway-api/) is enabled in Cilium, the absence of a check on the namespace in which a [ReferenceGrant](https://gateway-api.sigs.k8s.io/api-types/referencegrant/) is created could result in Cilium gaining visibility of secrets (including certificates) and services across namespaces.\n\nAn attacker on an affected cluster can configure Cilium to use cluster secrets or communicate with services that it should not have access to.\n\nGateway API functionality is disabled by default.\n\n### Patches\n\nThis vulnerability is fixed in Cilium release 1.13.4.\n\nCilium versions \u003c1.13 are not affected.\n\n### Workarounds\n\nThere is no workaround to this issue.\n\n### Acknowledgements\nThe Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to @meyskens for investigating and fixing the issue.\n\n### For more information\nIf you have any questions or comments about this advisory, please reach out on [Slack](https://docs.cilium.io/en/latest/community/community/#slack).\n\nAs usual, if you think you found a related vulnerability, we strongly encourage you to report security vulnerabilities to our private security mailing list: [security@cilium.io](mailto:security@cilium.io) - 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.\n","status":"published","published":"2023-06-16T17:47:56Z","modified":"2026-09-10T03:50:08.433582241Z","cvss":[{"version":"3.1","score":3.4,"vector":"CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N","level":"low"}],"cwes":["CWE-200"],"updated_at":"2026-11-02T15:46:55.480549Z"},{"id":"BIT-cilium-2023-34242","title":"Cilium vulnerable to information leakage via incorrect ReferenceGrant handling","description":"Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Prior to version 1.13.4, when Gateway API is enabled in Cilium, the absence of a check on the namespace in which a ReferenceGrant is created could result in Cilium unintentionally gaining visibility of secrets (including certificates) and services across namespaces. An attacker on an affected cluster can leverage this issue to use cluster secrets that should not be visible to them, or communicate with services that they should not have access to. Gateway API functionality is disabled by default. This vulnerability is fixed in Cilium release 1.13.4. As a workaround, restrict the creation of `ReferenceGrant` resources to admin users by using Kubernetes RBAC.","status":"published","published":"2024-05-15T12:07:15.578Z","modified":"2026-09-08T08:45:54.770989711Z","updated_at":"2026-11-02T15:28:28.70813Z"},{"id":"BIT-cilium-operator-2023-34242","title":"Cilium vulnerable to information leakage via incorrect ReferenceGrant handling","description":"Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Prior to version 1.13.4, when Gateway API is enabled in Cilium, the absence of a check on the namespace in which a ReferenceGrant is created could result in Cilium unintentionally gaining visibility of secrets (including certificates) and services across namespaces. An attacker on an affected cluster can leverage this issue to use cluster secrets that should not be visible to them, or communicate with services that they should not have access to. Gateway API functionality is disabled by default. This vulnerability is fixed in Cilium release 1.13.4. As a workaround, restrict the creation of `ReferenceGrant` resources to admin users by using Kubernetes RBAC.","status":"published","published":"2024-05-15T12:07:08.375Z","modified":"2026-09-08T08:45:54.429252735Z","updated_at":"2026-11-02T15:28:28.70813Z"},{"id":"BIT-cilium-proxy-2023-34242","description":"Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Prior to version 1.13.4, when Gateway API is enabled in Cilium, the absence of a check on the namespace in which a ReferenceGrant is created could result in Cilium unintentionally gaining visibility of secrets (including certificates) and services across namespaces. An attacker on an affected cluster can leverage this issue to use cluster secrets that should not be visible to them, or communicate with services that they should not have access to. Gateway API functionality is disabled by default. This vulnerability is fixed in Cilium release 1.13.4. As a workaround, restrict the creation of `ReferenceGrant` resources to admin users by using Kubernetes RBAC.","status":"published","published":"2024-07-01T11:12:35.098Z","modified":"2024-08-20T20:58:35.344825Z","updated_at":"2026-11-02T15:28:28.70813Z"},{"id":"BIT-hubble-2023-34242","description":"Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Prior to version 1.13.4, when Gateway API is enabled in Cilium, the absence of a check on the namespace in which a ReferenceGrant is created could result in Cilium unintentionally gaining visibility of secrets (including certificates) and services across namespaces. An attacker on an affected cluster can leverage this issue to use cluster secrets that should not be visible to them, or communicate with services that they should not have access to. Gateway API functionality is disabled by default. This vulnerability is fixed in Cilium release 1.13.4. As a workaround, restrict the creation of `ReferenceGrant` resources to admin users by using Kubernetes RBAC.","status":"published","published":"2024-06-04T09:44:33.815Z","modified":"2024-08-20T20:58:35.344825Z","updated_at":"2026-11-02T15:28:31.02759Z"},{"id":"BIT-hubble-relay-2023-34242","title":"Cilium vulnerable to information leakage via incorrect ReferenceGrant handling","description":"Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Prior to version 1.13.4, when Gateway API is enabled in Cilium, the absence of a check on the namespace in which a ReferenceGrant is created could result in Cilium unintentionally gaining visibility of secrets (including certificates) and services across namespaces. An attacker on an affected cluster can leverage this issue to use cluster secrets that should not be visible to them, or communicate with services that they should not have access to. Gateway API functionality is disabled by default. This vulnerability is fixed in Cilium release 1.13.4. As a workaround, restrict the creation of `ReferenceGrant` resources to admin users by using Kubernetes RBAC.","status":"published","published":"2024-05-24T19:22:36.388Z","modified":"2026-09-08T08:48:23.033820747Z","updated_at":"2026-11-02T15:28:31.02759Z"},{"id":"BIT-hubble-ui-2023-34242","description":"Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Prior to version 1.13.4, when Gateway API is enabled in Cilium, the absence of a check on the namespace in which a ReferenceGrant is created could result in Cilium unintentionally gaining visibility of secrets (including certificates) and services across namespaces. An attacker on an affected cluster can leverage this issue to use cluster secrets that should not be visible to them, or communicate with services that they should not have access to. Gateway API functionality is disabled by default. This vulnerability is fixed in Cilium release 1.13.4. As a workaround, restrict the creation of `ReferenceGrant` resources to admin users by using Kubernetes RBAC.","status":"published","published":"2024-07-01T11:17:34.097Z","modified":"2024-08-20T20:58:35.344825Z","updated_at":"2026-11-02T15:28:31.02759Z"},{"id":"BIT-hubble-ui-backend-2023-34242","description":"Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Prior to version 1.13.4, when Gateway API is enabled in Cilium, the absence of a check on the namespace in which a ReferenceGrant is created could result in Cilium unintentionally gaining visibility of secrets (including certificates) and services across namespaces. An attacker on an affected cluster can leverage this issue to use cluster secrets that should not be visible to them, or communicate with services that they should not have access to. Gateway API functionality is disabled by default. This vulnerability is fixed in Cilium release 1.13.4. As a workaround, restrict the creation of `ReferenceGrant` resources to admin users by using Kubernetes RBAC.","status":"published","published":"2024-07-01T11:17:37.096Z","modified":"2024-08-20T20:58:35.344825Z","updated_at":"2026-11-02T15:28:31.02759Z"},{"id":"GO-2023-1862","title":"Cilium vulnerable to information leakage via incorrect ReferenceGrant handling in github.com/cilium/cilium","description":"Cilium vulnerable to information leakage via incorrect ReferenceGrant handling in github.com/cilium/cilium","status":"published","published":"2024-08-20T20:31:35Z","modified":"2026-02-04T03:46:16.610915Z","updated_at":"2026-11-02T15:47:01.185262Z"}]}}