Allocation of Resources Without Limits or Throttling Affecting coredns-fips package, versions <1.12.2-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.06% (20th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Allocation of Resources Without Limits or Throttling vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-CHAINGUARDLATEST-COREDNSFIPS-10335848
  • published10 Jun 2025
  • disclosed6 Jun 2025

Introduced: 6 Jun 2025

NewCVE-2025-47950  (opens in a new tab)
CWE-770  (opens in a new tab)

How to fix?

Upgrade Chainguard coredns-fips to version 1.12.2-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream coredns-fips package and not the coredns-fips package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1