Debug mode leaks confidential data in Cilium
cilium
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/cilium/cilium Go |
|
|
cilium
| Product | Affected | Fixed in |
|---|---|---|
| github.com/cilium/cilium Go |
|
|
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.
From the CVE record · GitHub_M
When Cilium runs in debug mode, it can log contents of the `cilium-secrets` namespace, including TLS private keys. An attacker with access to Cilium container debug output could use those secrets to intercept and modify traffic to and from the affected cluster. Logging can occur on agent restart, secret modification, or creation of Ingress or GatewayAPI resources.
Teams running affected versions of the Go package `github.com/cilium/cilium` before the fixed Cilium releases 1.11.16, 1.12.9, and 1.13.2 should check their deployments.