Most recent entries from all

bdu:2025-06624

Withdrawn: CLEANSTART-2026-LS13491 — Security fixes in kubernetes-dns-node-cache-fips 1.26.0-r1

Withdrawn by the publisher.

Affected: CleanStart: kubernetes-dns-node-cache-fips

Package kubernetes-dns-node-cache-fips version 1.26.0-r1 fixes 18 vulnerabilities: CVE-2025-47950, CVE-2023-28452, CVE-2024-0874, CVE-2025-58063, ghsa-cvx7-x8pj-x2gw...

EUVD-2026-243316

fkie_cve-2025-47950

CoreDNS is a DNS server that chains plugins. In versions prior to 1.12.2, a Denial of Service (DoS) vulnerability exists in the CoreDNS DNS-over-QUIC (DoQ) server implementation. The server previously created a new goroutine for every incoming QUIC stream without imposing any limits on the number of concurrent streams or goroutines. A remote, unauthenticated attacker could open a large number of streams, leading to uncontrolled memory consumption and eventually causing an Out Of Memory (OOM) crash — especially in containerized or memory-constrained environments. The patch in version 1.12.2 introduces two key mitigation mechanisms: `max_streams`, which caps the number of concurrent QUIC streams per connection with a default value of `256`; and `worker_pool_size`, which Introduces a server-wide, bounded worker pool to process incoming streams with a default value of `1024`. This eliminates the 1:1 stream-to-goroutine model and ensures that CoreDNS remains resilient under high concurrency. Some workarounds are available for those who are unable to upgrade. Disable QUIC support by removing or commenting out the `quic://` block in the Corefile, use container runtime resource limits to detect and isolate excessive memory usage, and/or monitor QUIC connection patterns and alert on anomalies.

GHSA-cvx7-x8pj-x2gw — CoreDNS Vulnerable to DoQ Memory Exhaustion via Stream Amplification

Affected: Go: github.com/coredns/coredns

### Summary

A **Denial of Service (DoS)** vulnerability was discovered in the CoreDNS DNS-over-QUIC (DoQ) server implementation. The server previously created a new goroutine for every incoming QUIC stream without imposing any limits on the number of concurrent streams or goroutines. A remote, unauthenticated attacker could open a large number of streams, leading to uncontrolled memory consumption and eventually causing an Out Of Memory (OOM) crash — especially in containerized or memory-constrained environments.

### Impact

- **Component**: `server_quic.go` - **Attack Vector**: Remote, network-based - **Attack Complexity**: Low - **Privileges Required**: None - **User Interaction**: None - **Impact**: High availability loss (OOM kill or unresponsiveness)

This issue affects deployments with `quic://` enabled in the Corefile. A single attacker can cause the CoreDNS instance to become unresponsive using minimal bandwidth and CPU.

### Patches

The patch introduces two key mitigation mechanisms:

- **`max_streams`**: Caps the number of concurrent QUIC streams per connection. Default: `256`. - **`worker_pool_size`**: Introduces a server-wide, bounded worker pool to process incoming streams. Default: `1024`.

This eliminates the 1:1 stream-to-goroutine model and ensures that CoreDNS remains resilient under high concurrency. The new configuration options are exposed through the `quic` Corefile block:

``` quic { max_streams 256 worker_pool_size 1024 } ```

These default…

msrc_CVE-2025-47950 — CoreDNS Vulnerable to DoQ Memory Exhaustion via Stream Amplification

msrc_CVE-2025-47950

openSUSE-SU-2025:15225-1 — govulncheck-vulndb-0.0.20250612T141001-1.1 on GA media

govulncheck-vulndb-0.0.20250612T141001-1.1 on GA media

RHSA-2025:17128 — Red Hat Security Advisory: Submariner v0.20.2 security fixes and container updates

coredns: CoreDNS Vulnerable to DoQ Memory Exhaustion via Stream Amplification

WID-SEC-W-2025-1261 — CoreDNS: Schwachstelle ermöglicht Denial of Service

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in CoreDNS ausnutzen, um einen Denial of Service Angriff durchzuführen.