🛡️ CVE-2024-47825 — cilium

🟠 CVSS 8.0 — High ✅ No Known Exploit CWE-276 OSV
8.0
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

Cilium's CIDR deny policies may not take effect when a more narrow CIDR allow is present

Impact

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.

As an example, given the below policies, traffic is allowed to 1.1.1.2, when it should be denied:

```

apiVersion: cilium.io/v2

kind: CiliumClusterwideNetworkPolicy

metadata:

name: block-scary-range

spec:

endpointSelector: {}

egressDeny:

  • toCIDRSet:
  • cidr: 1.0.0.0/8

apiVersion: cilium.io/v2

kind: CiliumNetworkPolicy

metadata:

name: evade-deny

spec:

endpointSelector: {}

egress:

  • toCIDR:
  • 1.1.1.2/32
  • toEntities:
  • all

```

Patches

This issue affects:

  • Cilium v1.14 between v1.14.0 and v1.14.15 inclusive
  • Cilium v1.15 between v1.15.0 and v1.15.9 inclusive

This issue has been patched in:

  • Cilium v1.14.16
  • Cilium v1.15.10

Workarounds

Users with policies using enableDefaultDeny: false can work around this issue by removing this configuration option and explicitly defining any allow rules required.

No workaround is available to users with egress policies that explicitly specify toEntities: all.

Acknowledgements

The Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to @squeed, @christarazi, and @jrajahalme for their work in triaging and resolving this issue.

For more information

If you have any questions or comments about this advisory, please reach out on [Slack](https://docs.cilium.io/en/latest/community/community/#slack).

If you think you have found a vulnerability affecting Cilium, we strongly encourage you to report it to our security mailing list at [[email protected]](mailto:[email protected]). This is a private mailing list for the Cilium security team, and your report will be treated with top priority.

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is high, an attacker needs no privileges on the target. No user interaction is required. The scope is changed, meaning a successful attack can affect components beyond the vulnerable one. Rated impact: confidentiality low, integrity none, availability none.

Weakness class

CVE-2024-47825 is classified as CWE-276: Incorrect Default Permissions. Files or resources are created with permissions that are broader than they need to be.

Affected software

CVE-2024-47825 is recorded against 4 packages.

  • cilium
  • cilium-operator
  • github.com/cilium/cilium
  • hubble-relay

Timeline and source

Published on 23 October 2024 and last revised on 17 June 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

github.com (Web)
nvd.nist.gov (Web)

Details

Severity HIGH
CVSS Score 8.0
CVSS Vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N
CWE CWE-276
Public Exploit ✅ No
Source OSV
Published 2024-10-23
Updated 2026-08-12
Modified 2026-06-17
Fix URL N/A

Affected Packages

Software From version Fixed in
cilium
cilium-operator
github.com/cilium/cilium
hubble-relay

Site Security Check

Is cilium part of your stack?

CVE-2024-47825 is rated CVSS 8.0 High. BotEraser scans your installation against known CVE records and tells you whether this vulnerability applies to the versions you actually run.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.