Skip to content
OpenAdvisories
Medium · 5.8 CVE-2024-52529 BIT-cilium-2024-52529BIT-cilium-operator-2024-52529BIT-hubble-relay-2024-52529EUVD-2024-3391GHSA-xg58-75qf-9r67GO-2024-3290

Layer 7 policy enforcement may not occur in policies with wildcarded port ranges in Cilium

Published Nov 25, 2024 · Updated Nov 26, 2024 · Assigned by GitHub_M

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 products

VendorProductAffectedFixed
cilium cilium >= 1.16.0, < 1.16.4 —

Fixed in Linux distributions

Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.

ReleasePackageFixed inAdvisory
openSUSE Tumbleweed govulncheck-vulndb 0.0.20241209T183251-1.1 openSUSE-SU-2024:14567-1

Wolfi

ReleasePackageFixed inAdvisory
Wolfi rolling hubble 1.16.4-r0 —

Affected packages

EcosystemPackageAffectedFixedRecord
Go github.com/cilium/cilium >= 1.16.0, < 1.16.4 1.16.4 GHSA-xg58-75qf-9r67

Advisories 1

References