Layer 7 policy enforcement may not occur in policies with wildcarded port ranges in Cilium
Description
Cilium is a networking, observability, and security solution with an eBPF-based dataplane. For users with the following configuration: 1. An allow policy that selects a Layer 3 destination and a port range AND 2. A Layer 7 allow policy that selects a specific port within the first policy's range the Layer 7 enforcement would not occur for the traffic selected by the Layer 7 policy. This issue only affects users who use Cilium's port range functionality, which was introduced in Cilium v1.16. This issue is patched in PR #35150. This issue affects Cilium v1.16 between v1.16.0 and v1.16.3 inclusive. This issue is patched in Cilium v1.16.4. Users are advised to upgrade. Users with network policies that match the pattern described above can work around the issue by rewriting any policies that use port ranges to individually specify the ports permitted for traffic.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
github.com/cilium/ciliumGo | >= 1.16.0, < 1.16.4 | 1.16.4 |
Affected products
1Patches
0No patches discovered yet.
Vulnerability mechanics
AI mechanics synthesis has not run for this CVE yet.
References
4- github.com/advisories/GHSA-xg58-75qf-9r67ghsaADVISORY
- nvd.nist.gov/vuln/detail/CVE-2024-52529ghsaADVISORY
- github.com/cilium/cilium/pull/35150ghsax_refsource_MISCWEB
- github.com/cilium/cilium/security/advisories/GHSA-xg58-75qf-9r67ghsax_refsource_CONFIRMWEB
News mentions
0No linked articles in our index yet.