Schwachstellen / CVE-2026-35579

kritisch

CVE-2026-35579

github.com/coredns/coredns: CoreDNS: Authentication bypass allows unauthorized access to TSIG-protected functionalities

Veröffentlicht Geändert CWE 287, 303
In der Trivy Database seit spätestens 24. Okt. 2026, 07:11 UTCWann der Eintrag vor diesem Build hinzukam, ist nicht erfasst.

Einstufung nach Quelle

NVD9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
GHSA8.2CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Red Hat7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Trivys eigenes Label ist CRITICAL. Kritisch laut NVD, Photon OS. Niedriger laut GHSA (hoch), Red Hat (hoch), Azure Linux (hoch).

Beschreibung

CoreDNS is a DNS server written in Go. In versions prior to 1.14.3, the gRPC, QUIC, DoH, and DoH3 transport implementations incorrectly handle TSIG authentication. For gRPC and QUIC, the server checks whether the TSIG key name exists in the configuration but never calls dns.TsigVerify() to validate the HMAC. If the key name matches a configured key, the tsigStatus field remains nil and the tsig plugin treats the request as successfully authenticated regardless of the MAC value. For DoH and DoH3, the issue is more severe: the DoHWriter.TsigStatus() method unconditionally returns nil, and the server never inspects the TSIG record at all. Any request containing a TSIG record is treated as authenticated over DoH and DoH3, even if the key name is invalid and the MAC is arbitrary. An unauthenticated network attacker can exploit this to bypass TSIG-protected functionality such as AXFR/IXFR zone transfers, dynamic DNS updates, or other TSIG-gated plugin behavior. The DoH and DoH3 variants have a lower exploitation bar because the attacker does not need to know a valid TSIG key name. This issue has been fixed in version 1.14.3. As a workaround, disable gRPC, QUIC, DoH, and DoH3 listeners where TSIG authentication is required, or restrict network-level access to affected transport ports to trusted sources only.

Betroffene Pakete und behobene Versionen

QuellePaketBehoben in
Photon OS 4.0coredns1.14.3-1.ph4
Photon OS 5.0coredns1.11.1-16.1.ph5
Azure Linux 3.0coredns0:1.11.4-16.azl3
chainguardeks-distro-1.31, eks-distro-1.32, eks-distro-1.33 und 14 weitere1.31.43-r2 und 10 weitere
go::GitHub Security Advisory Gogithub.com/coredns/coredns1.14.3
minimoscoredns-1.14, coredns-fips-1.14, kubernetes-dns-node-cache und 1 weitere1.14.3-r0 und 1 weitere
rapidfort alpine 3.20coredns1.14.7-r0
rapidfort alpine 3.21coredns1.14.7-r0
rapidfort alpine 3.22coredns1.14.7-r0
rapidfort alpine 3.23coredns1.14.7-r0
rapidfort alpine 3.24coredns1.14.7-r0
wolfijuicefs-1.3, k8s_gateway, kubernetes-dns-node-cache1.3.1-r14 und 2 weitere
Alle 33 Einträge aus 12 Quellen zeigen
QuellePaketBehoben in
Photon OS 4.0coredns1.14.3-1.ph4
Photon OS 5.0coredns1.11.1-16.1.ph5
Azure Linux 3.0coredns0:1.11.4-16.azl3
chainguardeks-distro-1.311.31.43-r2
chainguardeks-distro-1.321.32.36-r2
chainguardeks-distro-1.331.33.26-r2
chainguardeks-distro-1.341.34.17-r2
chainguardeks-distro-1.351.35.8-r2
chainguardeks-distro-1.361.36.2-r6
chainguardeks-distro-fips-1.311.31.43-r2
chainguardeks-distro-fips-1.321.32.36-r2
chainguardeks-distro-fips-1.331.33.26-r2
chainguardeks-distro-fips-1.341.34.17-r2
chainguardeks-distro-fips-1.351.35.8-r2
chainguardeks-distro-fips-1.361.36.2-r5
chainguardjuicefs-1.31.3.1-r14
chainguardk8s_gateway1.8.0-r1
chainguardk8s_gateway-fips1.8.0-r1
chainguardkubernetes-dns-node-cache1.26.8-r3
chainguardkubernetes-dns-node-cache-fips1.26.8-r2
go::GitHub Security Advisory Gogithub.com/coredns/coredns1.14.3
minimoscoredns-1.141.14.3-r0
minimoscoredns-fips-1.141.14.3-r0
minimoskubernetes-dns-node-cache1.26.8-r1
minimoskubernetes-dns-node-cache-fips1.26.8-r1
rapidfort alpine 3.20coredns1.14.7-r0
rapidfort alpine 3.21coredns1.14.7-r0
rapidfort alpine 3.22coredns1.14.7-r0
rapidfort alpine 3.23coredns1.14.7-r0
rapidfort alpine 3.24coredns1.14.7-r0
wolfijuicefs-1.31.3.1-r14
wolfik8s_gateway1.8.0-r1
wolfikubernetes-dns-node-cache1.26.8-r3

Referenzen

Alle 9 Referenzen

Vulnerability data compiled from the Trivy vulnerability database (trivy-db, Aqua Security, Apache License 2.0), which aggregates third-party advisories. CVE records are published by The MITRE Corporation under the CVE Terms of Use; CVE is a trademark of MITRE. This product uses data from the NVD API but is not endorsed or certified by the NVD. Severity, titles and advisory data from the GitHub Advisory Database (CC BY 4.0), Red Hat security data (CC BY 4.0) and the other sources linked on each entry. Entries may be summarised or re-formatted; the linked original is the authoritative record.