Debug mode leaks confidential data in Cilium
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.11.16, 1.12.9, 1.13.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- cilium cilium
From 1.7 · fixed in 1.11.16; From 1.12.0 · fixed in 1.12.9; From 1.13.0 · fixed in 1.13.2
- github.com/cilium/ciliumGo
From 1.7.0 · through 1.10.0
- github.com/cilium/ciliumGo
From 1.11.0 · fixed in 1.11.16
- github.com/cilium/ciliumGo
From 1.12.0 · fixed in 1.12.9
- github.com/cilium/ciliumGo
From 1.13.0 · fixed in 1.13.2
- github.com/cilium/ciliumGo
From 1.7.0 · fixed in 1.11.16; From 1.12.0 · fixed in 1.12.9; From 1.13.0 · fixed in 1.13.2