Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

suse-cvrf логотип

openSUSE-SU-2026:20703-1

Опубликовано: 06 мая 2026
Источник: suse-cvrf

Описание

Security update for coredns

This update for coredns fixes the following issues:

Changes in coredns:

  • Update to version 1.14.3:
    • This release introduces Windows service support, along with full TSIG verification across DoH, DoH3, QUIC, and gRPC transports, and improved TSIG propagation and DoH request validation.
    • It also adds optional TLS for the metrics endpoint.
    • Performance and stability are improved through cache prefetching, QUIC optimizations, and a new max_age option in the forward plugin.
    • Additional updates include enhanced SVCB/HTTPS support, improved zone transfer behavior, and various DNSSEC, PROXY protocol, and concurrency fixes.
    • The release is built with Go 1.26.2, which includes security fixes addressing CVE-2026-32282, CVE-2026-32289, CVE-2026-33810, CVE-2026-27144, CVE-2026-27143, CVE-2026-32288, CVE-2026-32283, and CVE-2026-27140, and also includes fixes for CVE-2026-32936, CVE-2026-33190, CVE-2026-33489, CVE-2026-32934, and CVE-2026-35579.

Список пакетов

openSUSE Leap 16.0
coredns-1.14.3-bp160.1.1
coredns-extras-1.14.3-bp160.1.1

Описание

SWIG file names containing 'cgo' and well-crafted payloads could lead to code smuggling and arbitrary code execution at build time due to trust layer bypass.


Затронутые продукты
openSUSE Leap 16.0:coredns-1.14.3-bp160.1.1
openSUSE Leap 16.0:coredns-extras-1.14.3-bp160.1.1

Ссылки

Описание

Arithmetic over induction variables in loops were not correctly checked for underflow or overflow. As a result, the compiler would allow for invalid indexing to occur at runtime, potentially leading to memory corruption.


Затронутые продукты
openSUSE Leap 16.0:coredns-1.14.3-bp160.1.1
openSUSE Leap 16.0:coredns-extras-1.14.3-bp160.1.1

Ссылки

Описание

The compiler is meant to unwrap pointers which are the operands of a memory move; a no-op interface conversion prevented the compiler from making the correct determination about non-overlapping moves, potentially leading to memory corruption at runtime.


Затронутые продукты
openSUSE Leap 16.0:coredns-1.14.3-bp160.1.1
openSUSE Leap 16.0:coredns-extras-1.14.3-bp160.1.1

Ссылки

Описание

On Linux, if the target of Root.Chmod is replaced with a symlink while the chmod operation is in progress, Chmod can operate on the target of the symlink, even when the target lies outside the root. The Linux fchmodat syscall silently ignores the AT_SYMLINK_NOFOLLOW flag, which Root.Chmod uses to avoid symlink traversal. Root.Chmod checks its target before acting and returns an error if the target is a symlink lying outside the root, so the impact is limited to cases where the target is replaced with a symlink between the check and operation.


Затронутые продукты
openSUSE Leap 16.0:coredns-1.14.3-bp160.1.1
openSUSE Leap 16.0:coredns-extras-1.14.3-bp160.1.1

Ссылки

Описание

If one side of the TLS connection sends multiple key update messages post-handshake in a single record, the connection can deadlock, causing uncontrolled consumption of resources. This can lead to a denial of service. This only affects TLS 1.3.


Затронутые продукты
openSUSE Leap 16.0:coredns-1.14.3-bp160.1.1
openSUSE Leap 16.0:coredns-extras-1.14.3-bp160.1.1

Ссылки

Описание

tar.Reader can allocate an unbounded amount of memory when reading a maliciously-crafted archive containing a large number of sparse regions encoded in the "old GNU sparse map" format.


Затронутые продукты
openSUSE Leap 16.0:coredns-1.14.3-bp160.1.1
openSUSE Leap 16.0:coredns-extras-1.14.3-bp160.1.1

Ссылки

Описание

Context was not properly tracked across template branches for JS template literals, leading to possibly incorrect escaping of content when branches were used. Additionally template actions within JS template literals did not properly track the brace depth, leading to incorrect escaping being applied. These issues could cause actions within JS template literals to be incorrectly or improperly escaped, leading to XSS vulnerabilities.


Затронутые продукты
openSUSE Leap 16.0:coredns-1.14.3-bp160.1.1
openSUSE Leap 16.0:coredns-extras-1.14.3-bp160.1.1

Ссылки

Описание

CoreDNS is a DNS server that chains plugins. In versions prior to 1.14.3, the DNS-over-QUIC (DoQ) server can be driven into unbounded goroutine and memory growth by a remote client that opens many QUIC streams and sends only 1 byte per stream. When the worker pool is full, CoreDNS still spawns a goroutine per accepted stream to wait for a worker token. Additionally, active workers block indefinitely in io.ReadFull() with no per-stream read deadline, allowing an attacker to pin all workers by sending a single byte so the read blocks waiting for the second byte of the DoQ length prefix. This enables an unauthenticated remote attacker to cause memory exhaustion and OOM-kill. This issue has been fixed in version 1.14.3. No known workarounds exist.


Затронутые продукты
openSUSE Leap 16.0:coredns-1.14.3-bp160.1.1
openSUSE Leap 16.0:coredns-extras-1.14.3-bp160.1.1

Ссылки

Описание

CoreDNS is a DNS server that chains plugins. In versions prior to 1.14.3, the DNS-over-HTTPS (DoH) GET path accepts oversized dns= query parameter values and performs URL query parsing, base64 decoding, and DNS message unpacking before rejecting the request. Unlike the POST path, which applies a bounded read via http.MaxBytesReader limited to 65536 bytes, the GET path has no equivalent size validation before expensive processing. A remote, unauthenticated attacker can repeatedly send oversized DoH GET requests to force high CPU usage, large transient memory allocations, and elevated garbage-collection pressure, leading to denial of service. This issue has been fixed in version 1.14.3.


Затронутые продукты
openSUSE Leap 16.0:coredns-1.14.3-bp160.1.1
openSUSE Leap 16.0:coredns-extras-1.14.3-bp160.1.1

Ссылки

Описание

CoreDNS is a DNS server that chains plugins. In versions prior to 1.14.3, the tsig plugin can be bypassed on non-plain-DNS transports (DoT, DoH, DoH3, DoQ, and gRPC) because it trusts the transport writer's TsigStatus() instead of performing verification itself. The DoH and DoH3 writer's TsigStatus() always returns nil, the DoT server does not set TsigSecret on the dns.Server, and the DoQ and gRPC writers also unconditionally return nil. This allows an unauthenticated remote client to bypass TSIG-based authentication and access resources intended to be restricted behind a tsig require all policy. Plain DNS over TCP and UDP are not affected. This issue has been fixed in version 1.14.3.


Затронутые продукты
openSUSE Leap 16.0:coredns-1.14.3-bp160.1.1
openSUSE Leap 16.0:coredns-extras-1.14.3-bp160.1.1

Ссылки

Описание

CoreDNS is a DNS server that chains plugins. In versions prior to 1.14.3, the transfer plugin can select the wrong ACL stanza when both a parent zone and a more-specific subzone are configured. The longestMatch() function in plugin/transfer/transfer.go uses a lexicographic string comparison instead of an actual longest-suffix match to select the winning zone. As a result, a permissive parent-zone transfer rule can override a restrictive subzone rule depending on zone name ordering (e.g., "example.org." > "a.example.org." lexicographically). This allows an unauthorized remote client to perform AXFR/IXFR for the subzone and retrieve its full zone contents. This issue has been fixed in version 1.14.3.


Затронутые продукты
openSUSE Leap 16.0:coredns-1.14.3-bp160.1.1
openSUSE Leap 16.0:coredns-extras-1.14.3-bp160.1.1

Ссылки

Описание

When verifying a certificate chain containing excluded DNS constraints, these constraints are not correctly applied to wildcard DNS SANs which use a different case than the constraint. This only affects validation of otherwise trusted certificate chains, issued by a root CA in the VerifyOptions.Roots CertPool, or in the system certificate pool.


Затронутые продукты
openSUSE Leap 16.0:coredns-1.14.3-bp160.1.1
openSUSE Leap 16.0:coredns-extras-1.14.3-bp160.1.1

Ссылки

Описание

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.


Затронутые продукты
openSUSE Leap 16.0:coredns-1.14.3-bp160.1.1
openSUSE Leap 16.0:coredns-extras-1.14.3-bp160.1.1

Ссылки