VulnPulse

最新のセキュリティ情報

10月21日(水)

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.

10月6日(火)

10月1日(木)

9月29日(火)

  • 22:16リリース・告知PowerDNSPowerDNS Blog

    End of Life Announcement: Debian 11

    On the 31st of August of this year (2026) Debian 11 "Bullseye" reached the end of its Long Term Support period, at which point we consider Bullseye to be End of Life. As we do not want to support our software running in unpatched environments, we have stopped building for Debian Bullseye. After the 1st of January 2027, we will start removing all repositories for this unsupported distribution from https://repo.powerdns.com/ . Users are recommended to upgrade their systems to supported operating system versions, such as Debian 12 or 13, or RHEL 9, 10, or any of the popular derivatives of RHEL.

9月22日(火)

9月15日(火)

  • 21:45リリース・告知PowerDNSPowerDNS Blog

    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?

9月8日(火)

1月30日(火)

  • 08:00リリース・告知UnboundPowerDNSNLnet Labs

    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.