CVE-2023-41333 Bypass of namespace restrictions in CiliumNetworkPolicy
An attacker with namespace-level API access can bypass Cilium network policy restrictions to affect cluster-wide traffic, requiring an upgrade or admission webhook workaround.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2023-41333?
CVE-2023-41333 is a medium-severity missing authorization vulnerability in cilium, published on 26 Sep 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
Cilium is a networking, observability, and security solution with an eBPF-based dataplane. An attacker with the ability to create or modify CiliumNetworkPolicy objects in a particular namespace is able to affect traffic on an entire Cilium cluster, potentially bypassing policy enforcement in other namespaces. By using a crafted `endpointSelector` that uses the `DoesNotExist` operator on the `reserved:init` label, the attacker can create policies that bypass namespace restrictions and affect the entire Cilium cluster. This includes potentially allowing or denying all traffic. This attack requires API server access, as described in the Kubernetes API Server Attacker section of the Cilium Threat Model. This issue has been resolved in Cilium versions 1.14.2, 1.13.7, and 1.12.14. As a workaround an admission webhook can be used to prevent the use of `endpointSelectors` that use the `DoesNotExist` operator on the `reserved:init` label in CiliumNetworkPolicies.
Weakness: CWE-306
Which versions are affected by CVE-2023-41333?
14 open source packages ship an affected version, including github.com/cilium/cilium, cilium and cilium-operator. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
github.com/cilium/cilium Go | All versions | 1.12.14, 1.13.7, 1.14.2 |
github.com/cilium/cilium Go | All versions | 1.12.14 |
github.com/cilium/cilium Go | All versions | 1.12.14 |
github.com/cilium/cilium Go | From 1.13.0 | 1.13.7 |
github.com/cilium/cilium Go | From 1.13.0 | 1.13.7 |
github.com/cilium/cilium Go | From 1.14.0 | 1.14.2 |
8 more packages
github.com/cilium/cilium Go | From 1.14.0 | 1.14.2 |
cilium Bitnami | All versions | 1.12.14, 1.13.7, 1.14.2 |
cilium-operator Bitnami | All versions | 1.12.14, 1.13.7, 1.14.2 |
cilium-proxy Bitnami | All versions | 1.12.14, 1.13.7, 1.14.2 |
hubble Bitnami | All versions | 1.12.14, 1.13.7, 1.14.2 |
hubble-relay Bitnami | All versions | 1.12.14, 1.13.7, 1.14.2 |
hubble-ui Bitnami | All versions | 1.12.14, 1.13.7, 1.14.2 |
hubble-ui-backend Bitnami | All versions | 1.12.14, 1.13.7, 1.14.2 |
Products include Cilium Cilium.
How do I fix CVE-2023-41333?
Upgrade github.com/cilium/cilium to a fixed version for your release line: 1.12.14, 1.13.7 or 1.14.2.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2023-41333 being exploited?
There is no known exploitation of CVE-2023-41333 in the wild and no public exploit code.
Other vulnerabilities in cilium
- CVE-2026-49445 Cilium: Sensitive information disclosure and cluster disruption via local Envoy admin socket access
- CVE-2022-29178 Incorrect Default Permissions in Cilium
- CVE-2024-28860 Insecure IPsec transport encryption in Cilium
- CVE-2026-41520 Cillium exposes sensitive information included in the cilium-bugtool debug archive
- CVE-2024-37307 Cilium leaks sensitive information in cilium-bugtool
Sources
Also known as BIT-cilium-2023-41333, BIT-cilium-operator-2023-41333, BIT-cilium-proxy-2023-41333, BIT-hubble-2023-41333, BIT-hubble-relay-2023-41333, BIT-hubble-ui-2023-41333 and 3 more.