Skip to content
Fencer Intel
low 3.4

CVE-2023-34242 json

Cilium vulnerable to information leakage via incorrect ReferenceGrant handling

published 3y ago modified 2mo ago also 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

cvss
3.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 23%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/cilium/cilium 1.13.4
  • bitnami cilium 1.13.4
  • bitnami cilium-operator 1.13.4
  • bitnami cilium-proxy 1.13.4
  • bitnami hubble 1.13.4
  • bitnami hubble-relay 1.13.4
  • bitnami hubble-ui 1.13.4
  • bitnami hubble-ui-backend 1.13.4
  • cilium cilium 1.13.4

Is CVE-2023-34242 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.31% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-15).

CVSS scores

assigned by version score vector
CNA 3.1 3.4 CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N
GitHub 3.1 3.4 CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OSV 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/cilium/cilium
>=1.13.0, <1.13.4
1.13.4
bitnami cilium
<1.13.4
1.13.4
bitnami cilium-operator
<1.13.4
1.13.4
bitnami cilium-proxy
<1.13.4
1.13.4
bitnami hubble
<1.13.4
1.13.4
bitnami hubble-relay
<1.13.4
1.13.4
bitnami hubble-ui
<1.13.4
1.13.4
bitnami hubble-ui-backend
<1.13.4
1.13.4

Affected products

  • cilium cilium

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.