<div class="container">
<h1>Security update for bind</h1>
<table class="table table-striped table-bordered">
<tbody>
<tr>
<th>Announcement ID:</th>
<td>SUSE-SU-2024:2636-1</td>
</tr>
<tr>
<th>Rating:</th>
<td>important</td>
</tr>
<tr>
<th>References:</th>
<td>
<ul>
<li style="display: inline;">
<a href="https://bugzilla.suse.com/show_bug.cgi?id=1228255">bsc#1228255</a>
</li>
<li style="display: inline;">
<a href="https://bugzilla.suse.com/show_bug.cgi?id=1228256">bsc#1228256</a>
</li>
<li style="display: inline;">
<a href="https://bugzilla.suse.com/show_bug.cgi?id=1228257">bsc#1228257</a>
</li>
<li style="display: inline;">
<a href="https://bugzilla.suse.com/show_bug.cgi?id=1228258">bsc#1228258</a>
</li>
</ul>
</td>
</tr>
<tr>
<th>
Cross-References:
</th>
<td>
<ul>
<li style="display: inline;">
<a href="https://www.suse.com/security/cve/CVE-2024-0760.html">CVE-2024-0760</a>
</li>
<li style="display: inline;">
<a href="https://www.suse.com/security/cve/CVE-2024-1737.html">CVE-2024-1737</a>
</li>
<li style="display: inline;">
<a href="https://www.suse.com/security/cve/CVE-2024-1975.html">CVE-2024-1975</a>
</li>
<li style="display: inline;">
<a href="https://www.suse.com/security/cve/CVE-2024-4076.html">CVE-2024-4076</a>
</li>
</ul>
</td>
</tr>
<tr>
<th>CVSS scores:</th>
<td>
<ul class="list-group">
<li class="list-group-item">
<span class="cvss-reference">CVE-2024-0760</span>
<span class="cvss-source">
(
SUSE
):
</span>
<span class="cvss-score">7.5</span>
<span class="cvss-vector">CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H</span>
</li>
<li class="list-group-item">
<span class="cvss-reference">CVE-2024-1737</span>
<span class="cvss-source">
(
SUSE
):
</span>
<span class="cvss-score">7.5</span>
<span class="cvss-vector">CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H</span>
</li>
<li class="list-group-item">
<span class="cvss-reference">CVE-2024-1975</span>
<span class="cvss-source">
(
SUSE
):
</span>
<span class="cvss-score">7.5</span>
<span class="cvss-vector">CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H</span>
</li>
<li class="list-group-item">
<span class="cvss-reference">CVE-2024-4076</span>
<span class="cvss-source">
(
SUSE
):
</span>
<span class="cvss-score">7.5</span>
<span class="cvss-vector">CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H</span>
</li>
</ul>
</td>
</tr>
<tr>
<th>Affected Products:</th>
<td>
<ul class="list-group">
<li class="list-group-item">Basesystem Module 15-SP6</li>
<li class="list-group-item">openSUSE Leap 15.6</li>
<li class="list-group-item">Server Applications Module 15-SP6</li>
<li class="list-group-item">SUSE Linux Enterprise Desktop 15 SP6</li>
<li class="list-group-item">SUSE Linux Enterprise Real Time 15 SP6</li>
<li class="list-group-item">SUSE Linux Enterprise Server 15 SP6</li>
<li class="list-group-item">SUSE Linux Enterprise Server for SAP Applications 15 SP6</li>
</ul>
</td>
</tr>
</tbody>
</table>
<p>An update that solves four vulnerabilities can now be installed.</p>
<h2>Description:</h2>
<p>This update for bind fixes the following issues:</p>
<p>Update to release 9.18.28</p>
<p>Security fixes:</p>
<ul>
<li>CVE-2024-0760: Fixed a flood of DNS messages over TCP may make the server unstable (bsc#1228255)</li>
<li>CVE-2024-1737: Fixed BIND's database will be slow if a very large number of RRs exist at the same name (bsc#1228256)</li>
<li>CVE-2024-1975: Fixed SIG(0) can be used to exhaust CPU resources (bsc#1228257)</li>
<li>CVE-2024-4076: Fixed assertion failure when serving both stale cache data and authoritative zone content (bsc#1228258)</li>
</ul>
<p>Changelog:</p>
<ul>
<li>Command-line options for IPv4-only (named -4) and IPv6-only
(named -6) modes are now respected for zone primaries,
also-notify, and parental-agents.</li>
<li>An RPZ response’s SOA record TTL was set to 1 instead of the
SOA TTL, if add-soa was used. This has been fixed.</li>
<li>When a query related to zone maintenance (NOTIFY, SOA) timed
out close to a view shutdown (triggered e.g. by rndc reload),
named could crash with an assertion failure. This has been
fixed.</li>
<li>The statistics channel counters that indicated the number of
currently connected TCP IPv4/IPv6 clients were not properly
adjusted in certain failure scenarios. This has been fixed.</li>
<li>Some servers that could not be reached due to EHOSTDOWN or
ENETDOWN conditions were incorrectly prioritized during server
selection. These are now properly handled as unreachable.</li>
<li>On some systems the libuv call may return an error code when
sending a TCP reset for a connection, which triggers an
assertion failure in named. This error condition is now dealt
with in a more graceful manner, by logging the incident and
shutting down the connection.</li>
<li>Changes to listen-on statements were ignored on reconfiguration
unless the port or interface address was changed, making it
impossible to change a related listener transport type. That
issue has been fixed.</li>
<li>A bug in the keymgr code unintentionally slowed down some
DNSSEC key rollovers. This has been fixed.</li>
<li>Some ISO 8601 durations were accepted erroneously, leading to
shorter durations than expected. This has been fixed</li>
<li>A regression in cache-cleaning code enabled memory use to grow
significantly more quickly than before, until the configured
max-cache-size limit was reached. This has been fixed.</li>
<li>Using rndc flush inadvertently caused cache cleaning to become
less effective. This could ultimately lead to the configured
max-cache-size limit being exceeded and has now been fixed.</li>
<li>The logic for cleaning up expired cached DNS records was
tweaked to be more aggressive. This change helps with enforcing
max-cache-ttl and max-ncache-ttl in a timely manner.</li>
<li>It was possible to trigger a use-after-free assertion when the
overmem cache cleaning was initiated. This has been fixed.
New Features:</li>
<li>A new option signatures-jitter has been added to dnssec-policy
to allow signature expirations to be spread out over a period
of time.</li>
<li>The statistics channel now includes counters that indicate the
number of currently connected TCP IPv4/IPv6 clients.</li>
<li>Added RESOLVER.ARPA to the built in empty zones.
Feature Changes:</li>
<li>DNSSEC signatures that are not valid because the current time
falls outside the signature inception and expiration dates are
skipped instead of causing an immediate validation failure.
Security Fixes:</li>
<li>A malicious DNS client that sent many queries over TCP but
never read the responses could cause a server to respond slowly
or not at all for other clients. This has been fixed.
(CVE-2024-0760)</li>
<li>It is possible to craft excessively large resource records
sets, which have the effect of slowing down database
processing. This has been addressed by adding a configurable
limit to the number of records that can be stored per name and
type in a cache or zone database. The default is 100, which can
be tuned with the new max-records-per-type option.</li>
<li>It is possible to craft excessively large numbers of resource
record types for a given owner name, which has the effect of
slowing down database processing. This has been addressed by
adding a configurable limit to the number of records that can
be stored per name and type in a cache or zone database. The
default is 100, which can be tuned with the new
max-types-per-name option. (CVE-2024-1737)</li>
<li>Validating DNS messages signed using the SIG(0) protocol (RFC
2931) could cause excessive CPU load, leading to a
denial-of-service condition. Support for SIG(0) message
validation was removed from this version of named.
(CVE-2024-1975)</li>
<li>Due to a logic error, lookups that triggered serving stale data
and required lookups in local authoritative zone data could
have resulted in an assertion failure. This has been fixed.</li>
<li>Potential data races were found in our DoH implementation,
related to HTTP/2 session object management and endpoints set
object management after reconfiguration. These issues have been
fixed.</li>
<li>When looking up the NS records of parent zones as part of
looking up DS records, it was possible for named to trigger an
assertion failure if serve-stale was enabled. This has been
fixed. (CVE-2024-4076)</li>
</ul>
<h2>Patch Instructions:</h2>
<p>
To install this SUSE update use the SUSE recommended
installation methods like YaST online_update or "zypper patch".<br/>
Alternatively you can run the command listed for your product:
</p>
<ul class="list-group">
<li class="list-group-item">
Server Applications Module 15-SP6
<br/>
<code>zypper in -t patch SUSE-SLE-Module-Server-Applications-15-SP6-2024-2636=1</code>
</li>
<li class="list-group-item">
openSUSE Leap 15.6
<br/>
<code>zypper in -t patch SUSE-2024-2636=1 openSUSE-SLE-15.6-2024-2636=1</code>
</li>
<li class="list-group-item">
Basesystem Module 15-SP6
<br/>
<code>zypper in -t patch SUSE-SLE-Module-Basesystem-15-SP6-2024-2636=1</code>
</li>
</ul>
<h2>Package List:</h2>
<ul>
<li>
Server Applications Module 15-SP6 (aarch64 ppc64le s390x x86_64)
<ul>
<li>bind-debugsource-9.18.28-150600.3.3.1</li>
<li>bind-debuginfo-9.18.28-150600.3.3.1</li>
<li>bind-9.18.28-150600.3.3.1</li>
</ul>
</li>
<li>
Server Applications Module 15-SP6 (noarch)
<ul>
<li>bind-doc-9.18.28-150600.3.3.1</li>
</ul>
</li>
<li>
openSUSE Leap 15.6 (aarch64 ppc64le s390x x86_64 i586)
<ul>
<li>bind-utils-debuginfo-9.18.28-150600.3.3.1</li>
<li>bind-debuginfo-9.18.28-150600.3.3.1</li>
<li>bind-utils-9.18.28-150600.3.3.1</li>
<li>bind-9.18.28-150600.3.3.1</li>
<li>bind-debugsource-9.18.28-150600.3.3.1</li>
</ul>
</li>
<li>
openSUSE Leap 15.6 (noarch)
<ul>
<li>bind-doc-9.18.28-150600.3.3.1</li>
</ul>
</li>
<li>
Basesystem Module 15-SP6 (aarch64 ppc64le s390x x86_64)
<ul>
<li>bind-utils-debuginfo-9.18.28-150600.3.3.1</li>
<li>bind-debugsource-9.18.28-150600.3.3.1</li>
<li>bind-debuginfo-9.18.28-150600.3.3.1</li>
<li>bind-utils-9.18.28-150600.3.3.1</li>
</ul>
</li>
</ul>
<h2>References:</h2>
<ul>
<li>
<a href="https://www.suse.com/security/cve/CVE-2024-0760.html">https://www.suse.com/security/cve/CVE-2024-0760.html</a>
</li>
<li>
<a href="https://www.suse.com/security/cve/CVE-2024-1737.html">https://www.suse.com/security/cve/CVE-2024-1737.html</a>
</li>
<li>
<a href="https://www.suse.com/security/cve/CVE-2024-1975.html">https://www.suse.com/security/cve/CVE-2024-1975.html</a>
</li>
<li>
<a href="https://www.suse.com/security/cve/CVE-2024-4076.html">https://www.suse.com/security/cve/CVE-2024-4076.html</a>
</li>
<li>
<a href="https://bugzilla.suse.com/show_bug.cgi?id=1228255">https://bugzilla.suse.com/show_bug.cgi?id=1228255</a>
</li>
<li>
<a href="https://bugzilla.suse.com/show_bug.cgi?id=1228256">https://bugzilla.suse.com/show_bug.cgi?id=1228256</a>
</li>
<li>
<a href="https://bugzilla.suse.com/show_bug.cgi?id=1228257">https://bugzilla.suse.com/show_bug.cgi?id=1228257</a>
</li>
<li>
<a href="https://bugzilla.suse.com/show_bug.cgi?id=1228258">https://bugzilla.suse.com/show_bug.cgi?id=1228258</a>
</li>
</ul>
</div>