CVE-2024-25630GO-2024-2568BIT-CILIUM-2024-25630BIT-CILIUM-OPERATOR-2024-25630BIT-CILIUM-PROXY-2024-25630BIT-HUBBLE-2024-25630BIT-HUBBLE-RELAY-2024-25630BIT-HUBBLE-UI-2024-25630BIT-HUBBLE-UI-BACKEND-2024-25630GHSA-7496-FGV9-XW82
Cilium has unencrypted ingress/health traffic when using Wireguard transparent encryption
- 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.14.7
- 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
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Cilium is a networking, observability, and security solution with an eBPF-based dataplane. For Cilium users who are using CRDs to store Cilium state (the default configuration) and Wireguard transparent encryption, traffic to/from the Ingress and health endpoints is not encrypted. This issue affects Cilium v1.14 before v1.14.7 and has been patched in Cilium v1.14.7. There is no workaround to this issue.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- cilium cilium
From 1.14.0 · fixed in 1.14.7
- github.com/cilium/ciliumGo
From 1.14.0 · fixed in 1.14.7