CoreDNS
CoreDNS: Unauthenticated memory exhaustion in custom transports
CoreDNS is a DNS server written in Go. Prior to 1.14.7, the DNS-over-HTTPS, DNS-over-HTTP/3, DNS-over-QUIC, and DNS-over-gRPC request paths in plugin/pkg/doh/doh.go, core/dnsserver/server_quic.go, and core/dnsserver/server_grpc.go call dns.Msg.Unpack on attacker-controlled DNS section counts before dns.DefaultMsgAcceptFunc validates the fixed header. An unauthenticated client can use DNS name compression and excessive section counts to amplify allocation before the plugin chain, so plugin-level rate limiting cannot prevent concurrent requests from exhausting memory and terminating CoreDNS. The ordinary UDP and TCP listeners are not affected because they validate the header first. This issue is fixed in version 1.14.7.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 1.14.7
Fixed in 1.14.7
Mitigation
Upgrade coredns to 1.14.7 or later.
References
- Vendor advisory github.com/coredns/coredns/security/advisories…
- Patch github.com/coredns/coredns/commit/530b0a5ff2ad…
- Release notes github.com/coredns/coredns/releases/tag/v1.14.…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.