CVE-2023-30851GHSA-2H44-X2WX-49F4BIT-CILIUM-2023-30851BIT-CILIUM-OPERATOR-2023-30851BIT-CILIUM-PROXY-2023-30851BIT-HUBBLE-2023-30851BIT-HUBBLE-RELAY-2023-30851BIT-HUBBLE-UI-2023-30851BIT-HUBBLE-UI-BACKEND-2023-30851GO-2023-1785
Potential HTTP policy bypass when using header rules 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
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. This issue only impacts users who have a HTTP policy that applies to multiple `toEndpoints` AND have an allow-all rule in place that affects only one of those endpoints. In such cases, a wildcard rule will be appended to the set of HTTP rules, which could cause bypass of HTTP policies. This issue has been patched in Cilium 1.11.16, 1.12.9, and 1.13.2.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- cilium cilium
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
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
fixed in 1.11.16; From 1.12.0 · fixed in 1.12.9; From 1.13.0 · fixed in 1.13.2