CiliumLocalRedirectPolicy addressMatcher allows cross-namespace service traffic hijacking and can break service translation
- 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.17.16, 1.18.10, 1.19.4
- 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: partial
Summary
Cilium is a networking, observability, and security solution. Prior to 1.17.16, from 1.18.2 to 1.18.9, and from 1.19.0 to 1.19.3, users with the ability to create CiliumLocalRedirectPolicies can specify arbitrary ClusterIPs via addressMatcher, enabling hijacking traffic to Services in any namespace and bypassing namespace scoping enforced by serviceMatcher; deleting such a policy can also corrupt Cilium internal service state and stop service translation for the affected Service. This issue is fixed in versions 1.17.16, 1.18.10, and 1.19.4.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- cilium cilium
fixed in 1.17.16; From 1.18.2 · fixed in 1.18.10; From 1.19.0 · fixed in 1.19.4
- github.com/cilium/ciliumGo
From 1.19.0 · fixed in 1.19.4
- github.com/cilium/ciliumGo
From 1.18.2 · fixed in 1.18.10
- github.com/cilium/ciliumGo
fixed in 1.17.16
- github.com/cilium/ciliumGo
fixed in 1.17.16; From 1.18.2 · fixed in 1.18.10; From 1.19.0 · fixed in 1.19.4