SUSE-SU-2024:2862-1

Source
https://www.suse.com/support/update/announcement/2024/suse-su-20242862-1/
Import Source
https://ftp.suse.com/pub/projects/security/osv/SUSE-SU-2024:2862-1.json
JSON Data
https://api.test.osv.dev/v1/vulns/SUSE-SU-2024:2862-1
Related
Published
2024-08-09T07:20:35Z
Modified
2024-08-09T07:20:35Z
Summary
Security update for bind
Details

This update for bind fixes the following issues:

Update to 9.16.50:

  • Bug Fixes:
    • 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.
    • 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.
    • 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.
    • It was possible to trigger a use-after-free assertion when the overmem cache cleaning was initiated. This has been fixed. New Features:
    • Added RESOLVER.ARPA to the built in empty zones.
  • Security Fixes:
    • 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, bsc#1228256)
    • 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, bsc#1228257)
    • 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, bsc#1228258)
References

Affected packages

SUSE:Linux Enterprise Micro 5.5 / bind

Package

Name
bind
Purl
pkg:rpm/suse/bind&distro=SUSE%20Linux%20Enterprise%20Micro%205.5

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
9.16.50-150500.8.21.1

Ecosystem specific

{
    "binaries": [
        {
            "bind-utils": "9.16.50-150500.8.21.1",
            "python3-bind": "9.16.50-150500.8.21.1"
        }
    ]
}

SUSE:Linux Enterprise Module for Basesystem 15 SP5 / bind

Package

Name
bind
Purl
pkg:rpm/suse/bind&distro=SUSE%20Linux%20Enterprise%20Module%20for%20Basesystem%2015%20SP5

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
9.16.50-150500.8.21.1

Ecosystem specific

{
    "binaries": [
        {
            "bind-utils": "9.16.50-150500.8.21.1",
            "python3-bind": "9.16.50-150500.8.21.1"
        }
    ]
}

SUSE:Linux Enterprise Module for Server Applications 15 SP5 / bind

Package

Name
bind
Purl
pkg:rpm/suse/bind&distro=SUSE%20Linux%20Enterprise%20Module%20for%20Server%20Applications%2015%20SP5

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
9.16.50-150500.8.21.1

Ecosystem specific

{
    "binaries": [
        {
            "bind-doc": "9.16.50-150500.8.21.1",
            "bind": "9.16.50-150500.8.21.1"
        }
    ]
}

openSUSE:Leap 15.5 / bind

Package

Name
bind
Purl
pkg:rpm/opensuse/bind&distro=openSUSE%20Leap%2015.5

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
9.16.50-150500.8.21.1

Ecosystem specific

{
    "binaries": [
        {
            "bind-doc": "9.16.50-150500.8.21.1",
            "bind": "9.16.50-150500.8.21.1",
            "bind-utils": "9.16.50-150500.8.21.1",
            "python3-bind": "9.16.50-150500.8.21.1"
        }
    ]
}