Skip to content
Fencer Intel
medium 4.4

CVE-2023-27593 json

cilium-agent container can access the host via `hostPath` mount

published 3y ago modified 2mo ago also BIT-cilium-2023-27593 , BIT-cilium-operator-2023-27593 , BIT-cilium-proxy-2023-27593 , BIT-hubble-2023-27593 , BIT-hubble-relay-2023-27593 , BIT-hubble-ui-2023-27593 , BIT-hubble-ui-backend-2023-27593 , EUVD-2023-0865 , GHSA-4hc4-pgfx-3mrx

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

Summary

Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Prior to versions 1.11.15, 1.12.8, and 1.13.1, an attacker with access to a Cilium agent pod can write to `/opt/cni/bin` due to a `hostPath` mount of that directory in the agent pod. By replacing the CNI binary with their own malicious binary and waiting for the creation of a new pod on the node, the attacker can gain access to the underlying node.

The issue has been fixed and the fix is available on versions 1.11.15, 1.12.8, and 1.13.1. Some workarounds are available. Kubernetes RBAC should be used to deny users and service accounts `exec` access to Cilium agent pods. In cases where a user requires `exec` access to Cilium agent pods, but should not have access to the underlying node, no workaround is possible.

Patch / fix

  • go github.com/cilium/cilium 1.11.15, 1.12.8, 1.13.1
  • bitnami cilium 1.11.15, 1.12.8, 1.13.1
  • bitnami cilium-operator 1.11.15, 1.12.8, 1.13.1
  • bitnami cilium-proxy 1.11.15, 1.12.8, 1.13.1
  • bitnami hubble 1.11.15, 1.12.8, 1.13.1
  • bitnami hubble-relay 1.11.15, 1.12.8, 1.13.1
  • bitnami hubble-ui 1.11.15, 1.12.8, 1.13.1
  • bitnami hubble-ui-backend 1.11.15, 1.12.8, 1.13.1
  • cilium cilium 1.11.15, 1.12.8, 1.13.1

Is CVE-2023-27593 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.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-15).

CVSS scores

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

Affected packages

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

Affected products

  • cilium cilium

Classification

Weakness
  • CWE-276 Incorrect Default Permissions

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.