public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Cc: Matthias Fischer <matthias.fischer@ipfire.org>
Subject: [PATCH] bind: Update ot 9.20.15
Date: Fri, 24 Oct 2025 23:44:53 +0200	[thread overview]
Message-ID: <20251024214510.110137-1-matthias.fischer@ipfire.org> (raw)

For details see:

https://downloads.isc.org/isc/bind9/9.20.15/doc/arm/html/notes.html#notes-for-bind-9-20-15

Should anyone wonder where 9.20.14 has gone:
"The BIND 9.20.14 release was withdrawn after the discovery of a regression
in a security fix in it during pre-release testing."

"Notes for BIND 9.20.15
Security Fixes

    DNSSEC validation fails if matching but invalid DNSKEY is found.
    (CVE-2025-8677)

    Previously, if a matching but cryptographically invalid key was
    encountered during DNSSEC validation, the key was skipped and not
    counted towards validation failures. named now treats such DNSSEC keys
    as hard failures and the DNSSEC validation fails immediately, instead
    of continuing with the next DNSKEYs in the RRset.

    ISC would like to thank Zuyao Xu and Xiang Li from the All-in-One
    Security and Privacy Laboratory at Nankai University for bringing this
    vulnerability to our attention. [GL #5343]

    Address various spoofing attacks. (CVE-2025-40778)

    Previously, several issues could be exploited to poison a DNS cache
    with spoofed records for zones which were not DNSSEC-signed or if the
    resolver was configured to not do DNSSEC validation. These issues were
    assigned CVE-2025-40778 and have now been fixed.

    As an additional layer of protection, named no longer accepts DNAME
    records or extraneous NS records in the AUTHORITY section unless these
    are received via spoofing-resistant transport (TCP, UDP with DNS
    cookies, TSIG, or SIG(0)).

    ISC would like to thank Yuxiao Wu, Yunyi Zhang, Baojun Liu, and Haixin
    Duan from Tsinghua University for bringing this vulnerability to our
    attention. [GL #5414]

    Cache-poisoning due to weak pseudo-random number generator.
    (CVE-2025-40780)

    It was discovered during research for an upcoming academic paper that a
    xoshiro128** internal state can be recovered by an external 3rd party,
    allowing the prediction of UDP ports and DNS IDs in outgoing queries.
    This could lead to an attacker spoofing the DNS answers with great
    efficiency and poisoning the DNS cache.

    The internal random generator has been changed to a cryptographically
    secure pseudo-random generator.

    ISC would like to thank Prof. Amit Klein and Omer Ben Simhon from
    Hebrew University of Jerusalem for bringing this vulnerability to our
    attention. [GL #5484]

New Features

    Add dnssec-policy keys configuration check to named-checkconf.

    A new option -k was added to named-checkconf that allows checking the
    dnssec-policy keys configuration against the configured key stores. If
    the found key files are not in sync with the given dnssec-policy, the
    check will fail.

    This is useful to run before migrating to dnssec-policy. [GL #5486]

Bug Fixes

    Missing DNSSEC information when CD bit is set in query.

    The RRSIGs for glue records were not being cached correctly for CD=1
    queries. This has been fixed. [GL #5502]

    rndc sign during ZSK rollover will now replace signatures.

    When performing a ZSK rollover, if the new DNSKEY is omnipresent, the
    rndc sign command now signs the zone completely with the successor key,
    replacing all zone signatures from the predecessor key with new ones.
    [GL #5483]

    Use signer name when disabling DNSSEC algorithms.

    disable-algorithms could cause DNSSEC validation failures when the
    parent zone was signed with the algorithms that were being disabled for
    the child zone. This has been fixed; disable-algorithms now works on a
    whole-of-zone basis.

    If the zone's name is at or below the disable-algorithms name the
    algorithm is disabled for that zone, using deepest match when there are
    multiple disable-algorithms clauses. [GL #5165]

    Preserve cache when reload fails and reload the server again.

    This fixes an issue where failing to reconfigure/reload the server
    would fail to preserve the views' caches for subsequent server
    reconfigurations/reloads. [GL #5523]"

Signed-off-by: Matthias Fischer <matthias.fischer@ipfire.org>
---
 config/rootfiles/common/bind | 10 +++++-----
 lfs/bind                     |  4 ++--
 2 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/config/rootfiles/common/bind b/config/rootfiles/common/bind
index db57a9d40..eff7149ca 100644
--- a/config/rootfiles/common/bind
+++ b/config/rootfiles/common/bind
@@ -241,18 +241,18 @@ usr/bin/nsupdate
 #usr/include/ns/types.h
 #usr/include/ns/update.h
 #usr/include/ns/xfrout.h
-usr/lib/libdns-9.20.13.so
+usr/lib/libdns-9.20.15.so
 #usr/lib/libdns.la
 #usr/lib/libdns.so
-usr/lib/libisc-9.20.13.so
+usr/lib/libisc-9.20.15.so
 #usr/lib/libisc.la
 #usr/lib/libisc.so
-usr/lib/libisccc-9.20.13.so
+usr/lib/libisccc-9.20.15.so
 #usr/lib/libisccc.la
 #usr/lib/libisccc.so
-usr/lib/libisccfg-9.20.13.so
+usr/lib/libisccfg-9.20.15.so
 #usr/lib/libisccfg.la
 #usr/lib/libisccfg.so
-usr/lib/libns-9.20.13.so
+usr/lib/libns-9.20.15.so
 #usr/lib/libns.la
 #usr/lib/libns.so
diff --git a/lfs/bind b/lfs/bind
index 9befe9bfc..e5f8de750 100644
--- a/lfs/bind
+++ b/lfs/bind
@@ -25,7 +25,7 @@
 
 include Config
 
-VER        = 9.20.13
+VER        = 9.20.15
 
 THISAPP    = bind-$(VER)
 DL_FILE    = $(THISAPP).tar.xz
@@ -43,7 +43,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_BLAKE2 = c3738ebe468849293bec3d89499d7607b76fb636c7d21833dd56414fb569c1edfaa84d152ff9febfe0ebd5c65fa351423fbfbeaaee294d57949eb45631fd5623
+$(DL_FILE)_BLAKE2 = f272fc5e7a107b28cb71b55d2e87cfb2b215612c38289483044445f6c5ae57b0eb7003a368386122fb1fed551ac7be2e4e9bb34c2f8908e379e1aaf4e761c394
 
 install : $(TARGET)
 
-- 
2.43.0



                 reply	other threads:[~2025-10-24 21:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20251024214510.110137-1-matthias.fischer@ipfire.org \
    --to=matthias.fischer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox