Improper Handling of Exceptional Conditions Affecting cilium-1.16 package, versions <1.16.4-r0
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-CHAINGUARDLATEST-CILIUM116-8496586
- published11 Dec 2024
- disclosed25 Nov 2024
Introduced: 25 Nov 2024
CVE-2024-52529 (opens in a new tab)How to fix?
Upgrade Chainguard cilium-1.16 to version 1.16.4-r0 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream cilium-1.16 package and not the cilium-1.16 package as distributed by Chainguard.
See How to fix? for Chainguard relevant fixed versions and status.
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.