dbcve.org
CiliumApplication

CVE-2024-47825

HIGH · 8.7 CVSS v3.1 Published 2024-10-21
Fix available
A fix is available. Upgrade to 1.14.16 / 1.15.10 or later.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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`.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In Cilium versions 1.14.0 through 1.14.15 and prior to 1.15.10, a security policy rule that denies a network prefix broader than /32 can be silently ignored when paired with another policy rule referencing a narrower prefix (CIDRSet or toFQDN) that has either enableDefaultDeny: false or toEntities: all configured. This creates a policy bypass where the broader deny rule fails to enforce, allowing unintended network traffic.

MitigationUpgrade Cilium to version 1.14.16 or 1.15.10 or higher. As interim workarounds, remove enableDefaultDeny: false from policies and explicitly define allow rules, or replace toEntities: all with toEntities: world in egress policies.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CiliumApplication
Affected:>= 1.14.0, < 1.14.16>= 1.15.0, < 1.15.10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Cilium version
    Run 'cilium version' or check the Cilium operator/agent pod version via 'kubectl get pods -n kube-system -l k8s-app=cilium -o jsonpath="{.items[*].spec.containers[*].image}"'
    Affected if Version is >= 1.14.0 and < 1.14.16, or >= 1.15.0 and < 1.15.10
  2. Identify deny policies with broad CIDR
    Retrieve all CiliumNetworkPolicy and CiliumClusterwideNetworkPolicy resources: 'kubectl get cnp,ccnp -A -o yaml' and inspect for rules containing 'ingress' or 'egress' with 'deny' action and a 'cidr' field with prefix larger than /32 (e.g., '0.0.0.0/0', '::/0')
    Affected if A deny rule exists with a CIDR prefix covering a broad range (larger than a single IP)
  3. Check for conflicting CIDRSet or toFQDN rules
    In the same policy files, search for rules that contain either 'cidrSet' or 'toFQDN' alongside either 'enableDefaultDeny: false' or 'toEntities: all' in the same or another rule within the same policy
    Affected if A separate rule in the policy uses CIDRSet or toFQDN with enableDefaultDeny set to false, or specifies toEntities: all
  4. Verify policy coexistence
    Confirm that both the broad CIDR deny rule and the CIDRSet/toFQDN rule with enableDefaultDeny: false or toEntities: all exist within the same CiliumNetworkPolicy or CiliumClusterwideNetworkPolicy resource
    Affected if Both problematic rule patterns exist concurrently in any network policy in the cluster

You are affected if running a vulnerable Cilium version AND you have policies that combine a broad CIDR deny rule with a separate rule using CIDRSet or toFQDN that has enableDefaultDeny: false or toEntities: all.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.14.16 / 1.15.10 or later
Fixed in 1.14.161.15.10
Interim mitigation

Upgrade Cilium to version 1.14.16 or 1.15.10 or higher. As interim workarounds, remove enableDefaultDeny: false from policies and explicitly define allow rules, or replace toEntities: all with toEntities: world in egress policies.

Recommended fix High confidence

Cilium 1.14.16 (for 1.14.x branches) or Cilium 1.15.10 (for 1.15.x branches)

  1. Identify your current Cilium version using `cilium version` or checking your deployment manifests
  2. If running Cilium 1.14.x (>=1.14.0 and <1.14.16), upgrade to version 1.14.16
  3. If running Cilium 1.15.x (>=1.15.0 and <1.15.10), upgrade to version 1.15.10
  4. After upgrading, verify your network policies still function as expected by testing connectivity
  5. Alternatively, if immediate upgrade is not possible, review your CiliumNetworkPolicy resources: locate any rules with `enableDefaultDeny: false` and either remove this field or explicitly define all required allow rules; locate any rules with `toEntities: all` and change to `toEntities: world`
Caveat No explicit breaking changes mentioned for this security patch; always review release notes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cilium Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-47825 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-47825 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data