Skip to content
Fencer Intel
medium 5.8

CVE-2024-52529 json

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

published last yr. modified 2mo ago also BIT-cilium-2024-52529 , BIT-cilium-operator-2024-52529 , BIT-hubble-relay-2024-52529 , EUVD-2024-3391 , GHSA-xg58-75qf-9r67 , GO-2024-3290

cvss
5.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 44%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/cilium/cilium 1.16.4
  • bitnami cilium 1.16.4
  • bitnami cilium-operator 1.16.4
  • bitnami hubble-relay 1.16.4
  • cilium cilium 1.16.4
  • govulncheck-vulndb openSUSE Tumbleweed 0.0.20241209T183251-1.1

opensuse advisories openSUSE-SU-2024:14567-1

Is CVE-2024-52529 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.52% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 5.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
GitHub 3.1 5.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
NVD 3.1 5.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
OSV 3.1 5.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/cilium/cilium
>=1.16.0, <1.16.4
1.16.4
bitnami cilium
>=1.16.0, <1.16.4
1.16.4
bitnami cilium-operator
>=1.16.0, <1.16.4
1.16.4
bitnami hubble-relay
>=1.16.0, <1.16.4
1.16.4

Affected products

  • cilium cilium

Classification

Weakness
  • CWE-755 Improper Handling of Exceptional Conditions
  • CWE-862 Missing Authorization

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.