CVE-2025-23028
published 2025-01-22CVE-2025-23028: Cilium is a networking, observability, and security solution with an eBPF-based dataplane. A denial of service vulnerability affects versions 1.14.0 through…
PriorityP428medium5.3CVSS 3.1
AVNACLPRNUINSUCNINAL
EPSS
0.43%
37.2th percentile
Cilium is a networking, observability, and security solution with an eBPF-based dataplane. A denial of service vulnerability affects versions 1.14.0 through 1.14.7, 1.15.0 through 1.15.11, and 1.16.0 through 1.16.4. In a Kubernetes cluster where Cilium is configured to proxy DNS traffic, an attacker can crash Cilium agents by sending a crafted DNS response to workloads from outside the cluster. For traffic that is allowed but without using DNS-based policy, the dataplane will continue to pass traffic as configured at the time of the DoS. For workloads that have DNS-based policy configured, existing connections may continue to operate, and new connections made without relying on DNS resolution may continue to be established, but new connections which rely on DNS resolution may be disrupted. Any configuration changes that affect the impacted agent may not be applied until the agent is able to restart. This issue is fixed in Cilium v1.14.18, v1.15.12, and v1.16.5. No known workarounds are available.
Affected
9 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| cilium | cilium | — | — |
| cilium | cilium | — | — |
| cilium | cilium | — | — |
| cilium | cilium | >= 1.14.0 < 1.14.18 | 1.14.18 |
| cilium | cilium | >= 1.15.0 < 1.15.12 | 1.15.12 |
| cilium | cilium | >= 1.16.0 < 1.16.5 | 1.16.5 |
| github.com | cilium_cilium | >= 1.14.0 < 1.14.18 | 1.14.18 |
| github.com | cilium_cilium | >= 1.15.0 < 1.15.12 | 1.15.12 |
| github.com | cilium_cilium | >= 1.16.0 < 1.16.5 | 1.16.5 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
DoS in Cilium agent DNS proxy from crafted DNS responses in github.com/cilium/cilium
osv·2025-01-28
CVE-2025-23028 DoS in Cilium agent DNS proxy from crafted DNS responses in github.com/cilium/cilium
DoS in Cilium agent DNS proxy from crafted DNS responses in github.com/cilium/cilium
DoS in Cilium agent DNS proxy from crafted DNS responses in github.com/cilium/cilium
GHSA
DoS in Cilium agent DNS proxy from crafted DNS responses
ghsa·2025-01-22
CVE-2025-23028 [MEDIUM] CWE-770 DoS in Cilium agent DNS proxy from crafted DNS responses
DoS in Cilium agent DNS proxy from crafted DNS responses
### Impact
In a Kubernetes cluster where Cilium is configured to proxy DNS traffic, an attacker can crash Cilium agents by sending a crafted DNS response to workloads from outside the cluster.
For traffic that is allowed but without using DNS-based policy, the dataplane will continue to pass traffic as configured at the time of the DoS. For workloads that have DNS-based policy configured, existing connections may continue to operate, and new connections made without relying on DNS resolution may continue to be established, but new connections which rely on DNS resolution may be disrupted. Any configuration changes that affect the impacted agent may not be applied until the agent is able to restart.
### Patches
This issue affects
OSV
DoS in Cilium agent DNS proxy from crafted DNS responses
osv·2025-01-22
CVE-2025-23028 [MEDIUM] DoS in Cilium agent DNS proxy from crafted DNS responses
DoS in Cilium agent DNS proxy from crafted DNS responses
### Impact
In a Kubernetes cluster where Cilium is configured to proxy DNS traffic, an attacker can crash Cilium agents by sending a crafted DNS response to workloads from outside the cluster.
For traffic that is allowed but without using DNS-based policy, the dataplane will continue to pass traffic as configured at the time of the DoS. For workloads that have DNS-based policy configured, existing connections may continue to operate, and new connections made without relying on DNS resolution may continue to be established, but new connections which rely on DNS resolution may be disrupted. Any configuration changes that affect the impacted agent may not be applied until the agent is able to restart.
### Patches
This issue affects
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2025-01-22
Published