最新のセキュリティ情報
10月21日(水)
PowerDNS Security Advisory 2026-13 for PowerDNS Authoritative Server
Today, we are releasing three new versions of the PowerDNS Authoritative Server. These 4.9.18, 5.0.8 and 5.1.5 versions provide fixes for the following PowerDNS Security Advisory:
PowerDNS Security Advisory 2026-12 for PowerDNS Recursor
Today we have released PowerDNS Recursor 5.3.12 and 5.4.8. These releases provide fixes for PowerDNS Security Advisory 2026-12 for PowerDNS Recursor: Multiple issues There are several CVEs associated with this advisory, three with severity High and the remaining with severity Medium or Low .
10月12日(月)
PowerDNS DNSdist 2.1.3 and 2.0.11 Released
Today we released DNSdist 2.1.3 and 2.0.11, fixing several issues. The notable one fixes an issue where incoming DNS over TLS and DNS over HTTPS connections could have been wrongly terminated early, when the OpenSSL provider is in use. We advise all users providing DNS over TLS or DNS over HTTPS to upgrade, but to be clear this is NOT a security issue.
9月15日(火)
How Much Latency Does Your Security Add?
Security has become an essential part of the connectivity experience. Subscribers expect their internet providers to deliver a connection that is fast and reliable, but also secure and protected. For operators, this creates an important challenge: How do you add security without compromising the performance your subscribers expect, and that you have worked hard to optimize?
1月30日(火)
The peculiar case of NSEC processing using expanded wildcard records
We discovered a vulnerability in the processing of wildcard synthesized NSEC records. The result was Unbound, Google public DNS, PowerDNS and Dnsmasq contained a flaw that made it possible to downgrade secure connections. While synthesis of NSEC records is allowed by RFC 4592 , these synthesized owner names should not be used in the NSEC processing. This does, however, happen in Unbound 1.6.7 and earlier versions. Ralph Dolmans wrote a blog post about the discovery and findings.