CVE-2022-29178High· 8.8▾ TwilightAccess to Unix domain socket can lead to privileges escalation in Cilium
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 48.4 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Sep 12.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
0.3%
0.3% → 0.3%
Users with host file system access on a node and the privileges to run as group ID 1000 can gain access to the per node API of Cilium via Unix domain socket on the host where Cilium is running. If a malicious user is able to gain unprivileged access to a user corresponding to this group, then they can leverage this access to compromise the integrity as well as system availability on that host. Operating Systems that have unprivileged users not belonging the group ID 1000 are not affected by this vulnerability.
Best practices for managing the secure deployment of Kubernetes clusters will typically limit the ability for a malicious user to deploy pods with access to this group or to access the host filesystem, and limit user access to the nodes for users belonging to this group. These best practices include (but are not limited to) enforcing Admission Control policies to limit the configuration of Kubernetes Pod hostPath and SecurityContext fields.
Cilium versions >=1.9.16, >=1.10.11, >=1.11.5 mitigate this issue by setting the default group to 0 (root).
Prevent Cilium from running with group 1000 by modifying Cilium's DaemonSet to run with the following command:
containers:
- name: cilium-agent
args:
- -c
- "groupdel cilium && cilium-agent --config-dir=/tmp/cilium/config-map"
command:
- bash
instead of
containers:
- name: cilium-agent
args:
- --config-dir=/tmp/cilium/config-map
command:
- cilium-agent
The Cilium community has worked together with members of Isovalent and Form 3 to prepare these mitigations. Special thanks to Daniel Iziourov and Daniel Teixeira for their cooperation.
If you have any questions or comments about this advisory:
github.com/cilium/cilium >= 1.11.0, < 1.11.5github.com/cilium/cilium >= 1.10.0, < 1.10.11github.com/cilium/cilium < 1.9.16Upgrade to a patched release:
github.com/cilium/cilium 1.11.5github.com/cilium/cilium 1.10.11github.com/cilium/cilium 1.9.16Connected by shared product, vendor, weakness, or advisory.
CVE-2024-25630Medium· 6.1Unencrypted ingress/health traffic when using Wireguard transparent encryption
CVE-2024-28248High· 7.2Intermittent HTTP policy bypass
CVE-2025-32793Medium· 4.0In Cilium, packets from terminating endpoints may not be encrypted in Wireguard-enabled clusters
CVE-2023-41333Medium· 6.9Cilium vulnerable to bypass of namespace restrictions in CiliumNetworkPolicy
CVE-2023-27593Medium· 4.4cilium-agent container can access the host via `hostPath` mount
CVE-2024-47825Medium· 4.0Cilium's CIDR deny policies may not take effect when a more narrow CIDR allow is present