CVE-2023-29002 Debug mode leaks confidential data in Cilium
Attackers with debug access can read sensitive secrets like TLS keys from Cilium logs, enabling traffic interception and modification.
- 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-29002?
CVE-2023-29002 is a high-severity vulnerability in cilium, published on 18 Apr 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. When run in debug mode, Cilium will log the contents of the `cilium-secrets` namespace. This could include data such as TLS private keys for Ingress and GatewayAPI resources. An attacker with access to debug output from the Cilium containers could use the resulting output to intercept and modify traffic to and from the affected cluster. Output of the sensitive information would occur at Cilium agent restart, when secrets in the namespace are modified, and on creation of Ingress or GatewayAPI resources. This vulnerability is fixed in Cilium releases 1.11.16, 1.12.9, and 1.13.2. Users unable to upgrade should disable debug mode.
Weakness: CWE-532
Which versions are affected by CVE-2023-29002?
16 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 | From 1.11.0 | 1.11.16 |
github.com/cilium/cilium Go | From 1.11.0 | 1.11.16 |
github.com/cilium/cilium Go | From 1.12.0 | 1.12.9 |
github.com/cilium/cilium Go | From 1.12.0 | 1.12.9 |
github.com/cilium/cilium Go | From 1.13.0 | 1.13.2 |
github.com/cilium/cilium Go | From 1.13.0 | 1.13.2 |
10 more packages
github.com/cilium/cilium Go | From 1.7.0 | 1.11.16, 1.12.9, 1.13.2 |
github.com/cilium/cilium Go | From 1.7.0 to 1.10.0 | None |
github.com/cilium/cilium Go | From 1.7.0 to 1.10.0 | None |
cilium Bitnami | From 1.7.0 | 1.11.16, 1.12.9, 1.13.2 |
cilium-operator Bitnami | From 1.7.0 | 1.11.16, 1.12.9, 1.13.2 |
cilium-proxy Bitnami | From 1.7.0 | 1.11.16, 1.12.9, 1.13.2 |
hubble Bitnami | From 1.7.0 | 1.11.16, 1.12.9, 1.13.2 |
hubble-relay Bitnami | From 1.7.0 | 1.11.16, 1.12.9, 1.13.2 |
hubble-ui Bitnami | From 1.7.0 | 1.11.16, 1.12.9, 1.13.2 |
hubble-ui-backend Bitnami | From 1.7.0 | 1.11.16, 1.12.9, 1.13.2 |
Products include Cilium Cilium.
How do I fix CVE-2023-29002?
Upgrade github.com/cilium/cilium to a fixed version for your release line: 1.11.16, 1.12.9 or 1.13.2.
Is CVE-2023-29002 being exploited?
There is no known exploitation of CVE-2023-29002 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-29002, BIT-cilium-operator-2023-29002, BIT-cilium-proxy-2023-29002, BIT-hubble-2023-29002, BIT-hubble-relay-2023-29002, BIT-hubble-ui-2023-29002 and 3 more.