{"schema_version":"1.9.0","id":"BIT-cilium-2024-47825","published":"2024-10-23T07:08:30.083Z","modified":"2026-09-08T08:45:56.006601747Z","aliases":["BIT-cilium-operator-2024-47825","BIT-hubble-relay-2024-47825","CVE-2024-47825","GHSA-3wwx-63fv-pfq6","GO-2024-3208"],"summary":"CIDR deny policies may not take effect when a more narrow CIDR allow is present","details":"Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Starting in version 1.14.0 and prior to versions 1.14.16 and 1.15.10, a policy rule denying a prefix that is broader than `/32` may be ignored if there is a policy rule referencing a more narrow prefix (`CIDRSet` or `toFQDN`) and this narrower policy rule specifies either `enableDefaultDeny: false` or `- toEntities: all`. Note that a rule specifying `toEntities: world` or `toEntities: 0.0.0.0/0` is insufficient, it must be to entity `all`.This issue has been patched in Cilium v1.14.16 and v1.15.10. As this issue only affects policies using `enableDefaultDeny: false` or that set `toEntities` to `all`, some workarounds are available. For users with policies using `enableDefaultDeny: false`, remove this configuration option and explicitly define any allow rules required. For users with egress policies that explicitly specify `toEntities: all`, use `toEntities: world`.","affected":[{"package":{"name":"cilium","ecosystem":"Bitnami","purl":"pkg:bitnami/cilium"},"ranges":[{"type":"SEMVER","events":[{"introduced":"1.15.4"},{"fixed":"1.16.0"}]}],"database_specific":{"source":"https://github.com/bitnami/vulndb/tree/main/data/cilium/BIT-cilium-2024-47825.json"},"severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N"}]}],"references":[{"type":"ADVISORY","url":"https://github.com/cilium/cilium/security/advisories/GHSA-3wwx-63fv-pfq6"},{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47825"}],"database_specific":{"cpes":["cpe:2.3:a:cilium:cilium:*:*:*:*:*:go:*:*"],"severity":"High"}}