Insecure IPsec transport encryption 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.14.9, 1.15.3, 1.13.14
- 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. Users of IPsec transparent encryption in Cilium may be vulnerable to cryptographic attacks that render the transparent encryption ineffective. In particular, Cilium is vulnerable to chosen plaintext, key recovery, replay attacks by a man-in-the-middle attacker. These attacks are possible due to an ESP sequence number collision when multiple nodes are configured with the same key. Fixed versions of Cilium use unique keys for each IPsec tunnel established between nodes, resolving all of the above attacks. This vulnerability is fixed in 1.13.13, 1.14.9, and 1.15.3.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- cilium cilium
From 1.4.0 · through 1.13.14; From 1.14.0 · fixed in 1.14.9; From 1.15.0 · fixed in 1.15.3
- github.com/cilium/ciliumGo
fixed in 1.13.14; From 1.14.0 · fixed in 1.14.9; From 1.15.0 · fixed in 1.15.3
- github.com/cilium/ciliumGo
From 1.4.0 · fixed in 1.13.14
- github.com/cilium/ciliumGo
From 1.14.0 · fixed in 1.14.9
- github.com/cilium/ciliumGo
From 1.15.0 · fixed in 1.15.3