<?xml version="1.0" encoding="UTF-8"?>
<cvrfdoc xmlns="http://www.icasi.org/CVRF/schema/cvrf/1.1" xmlns:cvrf="http://www.icasi.org/CVRF/schema/cvrf/1.1">
	<DocumentTitle xml:lang="en">An update for bind is now available for openEuler-22.03-LTS-SP1</DocumentTitle>
	<DocumentType>Security Advisory</DocumentType>
	<DocumentPublisher Type="Vendor">
		<ContactDetails>openeuler-security@openeuler.org</ContactDetails>
		<IssuingAuthority>openEuler security committee</IssuingAuthority>
	</DocumentPublisher>
	<DocumentTracking>
		<Identification>
			<ID>openEuler-SA-2024-1324</ID>
		</Identification>
		<Status>Final</Status>
		<Version>1.0</Version>
		<RevisionHistory>
			<Revision>
				<Number>1.0</Number>
				<Date>2024-03-22</Date>
				<Description>Initial</Description>
			</Revision>
		</RevisionHistory>
		<InitialReleaseDate>2024-03-22</InitialReleaseDate>
		<CurrentReleaseDate>2024-03-22</CurrentReleaseDate>
		<Generator>
			<Engine>openEuler SA Tool V1.0</Engine>
			<Date>2024-03-22</Date>
		</Generator>
	</DocumentTracking>
	<DocumentNotes>
		<Note Title="Synopsis" Type="General" Ordinal="1" xml:lang="en">bind security update</Note>
		<Note Title="Summary" Type="General" Ordinal="2" xml:lang="en">An update for bind is now available for openEuler-22.03-LTS-SP1.</Note>
		<Note Title="Description" Type="General" Ordinal="3" xml:lang="en">Berkeley Internet Name Domain (BIND) is an implementation of the Domain Name System (DNS) protocols and provides an openly redistributable reference implementation of the major components of the Domain Name System. This package includes the components to operate a DNS server.

Security Fix(es):

The DNS message parsing code in `named` includes a section whose computational complexity is overly high. It does not cause problems for typical DNS traffic, but crafted queries and responses may cause excessive CPU load on the affected `named` instance by exploiting this flaw. This issue affects both authoritative servers and recursive resolvers.
This issue affects BIND 9 versions 9.0.0 through 9.16.45, 9.18.0 through 9.18.21, 9.19.0 through 9.19.19, 9.9.3-S1 through 9.11.37-S1, 9.16.8-S1 through 9.16.45-S1, and 9.18.11-S1 through 9.18.21-S1.(CVE-2023-4408)

Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote attackers to cause a denial of service (CPU consumption) via one or more DNSSEC responses, aka the &quot;KeyTrap&quot; issue. One of the concerns is that, when there is a zone with many DNSKEY and RRSIG records, the protocol specification implies that an algorithm must evaluate all combinations of DNSKEY and RRSIG records.(CVE-2023-50387)

A flaw in query-handling code can cause `named` to exit prematurely with an assertion failure when:

  - `nxdomain-redirect &lt;domain&gt;;` is configured, and
  - the resolver receives a PTR query for an RFC 1918 address that would normally result in an authoritative NXDOMAIN response.
This issue affects BIND 9 versions 9.12.0 through 9.16.45, 9.18.0 through 9.18.21, 9.19.0 through 9.19.19, 9.16.8-S1 through 9.16.45-S1, and 9.18.11-S1 through 9.18.21-S1.(CVE-2023-5517)

A bad interaction between DNS64 and serve-stale may cause `named` to crash with an assertion failure during recursive resolution, when both of these features are enabled.
This issue affects BIND 9 versions 9.16.12 through 9.16.45, 9.18.0 through 9.18.21, 9.19.0 through 9.19.19, 9.16.12-S1 through 9.16.45-S1, and 9.18.11-S1 through 9.18.21-S1.(CVE-2023-5679)

To keep its cache database efficient, `named` running as a recursive resolver occasionally attempts to clean up the database. It uses several methods, including some that are asynchronous: a small chunk of memory pointing to the cache element that can be cleaned up is first allocated and then queued for later processing. It was discovered that if the resolver is continuously processing query patterns triggering this type of cache-database maintenance, `named` may not be able to handle the cleanup events in a timely manner. This in turn enables the list of queued cleanup events to grow infinitely large over time, allowing the configured `max-cache-size` limit to be significantly exceeded.
This issue affects BIND 9 versions 9.16.0 through 9.16.45 and 9.16.8-S1 through 9.16.45-S1.(CVE-2023-6516)</Note>
		<Note Title="Topic" Type="General" Ordinal="4" xml:lang="en">An update for bind is now available for openEuler-22.03-LTS-SP1.

openEuler Security has rated this update as having a security impact of high. A Common Vunlnerability Scoring System(CVSS)base score,which gives a detailed severity rating, is available for each vulnerability from the CVElink(s) in the References section.</Note>
		<Note Title="Severity" Type="General" Ordinal="5" xml:lang="en">High</Note>
		<Note Title="Affected Component" Type="General" Ordinal="6" xml:lang="en">bind</Note>
	</DocumentNotes>
	<DocumentReferences>
		<Reference Type="Self">
			<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1324</URL>
		</Reference>
		<Reference Type="openEuler CVE">
			<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2023-4408</URL>
			<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2023-50387</URL>
			<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2023-5517</URL>
			<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2023-5679</URL>
			<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2023-6516</URL>
		</Reference>
		<Reference Type="Other">
			<URL>https://nvd.nist.gov/vuln/detail/CVE-2023-4408</URL>
			<URL>https://nvd.nist.gov/vuln/detail/CVE-2023-50387</URL>
			<URL>https://nvd.nist.gov/vuln/detail/CVE-2023-5517</URL>
			<URL>https://nvd.nist.gov/vuln/detail/CVE-2023-5679</URL>
			<URL>https://nvd.nist.gov/vuln/detail/CVE-2023-6516</URL>
		</Reference>
	</DocumentReferences>
	<ProductTree xmlns="http://www.icasi.org/CVRF/schema/prod/1.1">
		<Branch Type="Product Name" Name="openEuler">
			<FullProductName ProductID="openEuler-22.03-LTS-SP1" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">openEuler-22.03-LTS-SP1</FullProductName>
		</Branch>
		<Branch Type="Package Arch" Name="aarch64">
			<FullProductName ProductID="bind-pkcs11-9.16.23-21" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">bind-pkcs11-9.16.23-21.oe2203sp1.aarch64.rpm</FullProductName>
			<FullProductName ProductID="bind-chroot-9.16.23-21" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">bind-chroot-9.16.23-21.oe2203sp1.aarch64.rpm</FullProductName>
			<FullProductName ProductID="bind-libs-9.16.23-21" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">bind-libs-9.16.23-21.oe2203sp1.aarch64.rpm</FullProductName>
			<FullProductName ProductID="bind-devel-9.16.23-21" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">bind-devel-9.16.23-21.oe2203sp1.aarch64.rpm</FullProductName>
			<FullProductName ProductID="bind-pkcs11-devel-9.16.23-21" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">bind-pkcs11-devel-9.16.23-21.oe2203sp1.aarch64.rpm</FullProductName>
			<FullProductName ProductID="bind-debuginfo-9.16.23-21" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">bind-debuginfo-9.16.23-21.oe2203sp1.aarch64.rpm</FullProductName>
			<FullProductName ProductID="bind-9.16.23-21" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">bind-9.16.23-21.oe2203sp1.aarch64.rpm</FullProductName>
			<FullProductName ProductID="bind-pkcs11-utils-9.16.23-21" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">bind-pkcs11-utils-9.16.23-21.oe2203sp1.aarch64.rpm</FullProductName>
			<FullProductName ProductID="bind-utils-9.16.23-21" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">bind-utils-9.16.23-21.oe2203sp1.aarch64.rpm</FullProductName>
			<FullProductName ProductID="bind-dnssec-utils-9.16.23-21" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">bind-dnssec-utils-9.16.23-21.oe2203sp1.aarch64.rpm</FullProductName>
			<FullProductName ProductID="bind-pkcs11-libs-9.16.23-21" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">bind-pkcs11-libs-9.16.23-21.oe2203sp1.aarch64.rpm</FullProductName>
			<FullProductName ProductID="bind-debugsource-9.16.23-21" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">bind-debugsource-9.16.23-21.oe2203sp1.aarch64.rpm</FullProductName>
		</Branch>
		<Branch Type="Package Arch" Name="noarch">
			<FullProductName ProductID="python3-bind-9.16.23-21" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">python3-bind-9.16.23-21.oe2203sp1.noarch.rpm</FullProductName>
			<FullProductName ProductID="bind-license-9.16.23-21" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">bind-license-9.16.23-21.oe2203sp1.noarch.rpm</FullProductName>
			<FullProductName ProductID="bind-dnssec-doc-9.16.23-21" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">bind-dnssec-doc-9.16.23-21.oe2203sp1.noarch.rpm</FullProductName>
		</Branch>
		<Branch Type="Package Arch" Name="src">
			<FullProductName ProductID="bind-9.16.23-21" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">bind-9.16.23-21.oe2203sp1.src.rpm</FullProductName>
		</Branch>
		<Branch Type="Package Arch" Name="x86_64">
			<FullProductName ProductID="bind-debuginfo-9.16.23-21" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">bind-debuginfo-9.16.23-21.oe2203sp1.x86_64.rpm</FullProductName>
			<FullProductName ProductID="bind-chroot-9.16.23-21" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">bind-chroot-9.16.23-21.oe2203sp1.x86_64.rpm</FullProductName>
			<FullProductName ProductID="bind-pkcs11-libs-9.16.23-21" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">bind-pkcs11-libs-9.16.23-21.oe2203sp1.x86_64.rpm</FullProductName>
			<FullProductName ProductID="bind-pkcs11-devel-9.16.23-21" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">bind-pkcs11-devel-9.16.23-21.oe2203sp1.x86_64.rpm</FullProductName>
			<FullProductName ProductID="bind-debugsource-9.16.23-21" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">bind-debugsource-9.16.23-21.oe2203sp1.x86_64.rpm</FullProductName>
			<FullProductName ProductID="bind-utils-9.16.23-21" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">bind-utils-9.16.23-21.oe2203sp1.x86_64.rpm</FullProductName>
			<FullProductName ProductID="bind-pkcs11-9.16.23-21" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">bind-pkcs11-9.16.23-21.oe2203sp1.x86_64.rpm</FullProductName>
			<FullProductName ProductID="bind-dnssec-utils-9.16.23-21" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">bind-dnssec-utils-9.16.23-21.oe2203sp1.x86_64.rpm</FullProductName>
			<FullProductName ProductID="bind-pkcs11-utils-9.16.23-21" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">bind-pkcs11-utils-9.16.23-21.oe2203sp1.x86_64.rpm</FullProductName>
			<FullProductName ProductID="bind-9.16.23-21" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">bind-9.16.23-21.oe2203sp1.x86_64.rpm</FullProductName>
			<FullProductName ProductID="bind-libs-9.16.23-21" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">bind-libs-9.16.23-21.oe2203sp1.x86_64.rpm</FullProductName>
			<FullProductName ProductID="bind-devel-9.16.23-21" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">bind-devel-9.16.23-21.oe2203sp1.x86_64.rpm</FullProductName>
		</Branch>
	</ProductTree>
	<Vulnerability Ordinal="1" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
		<Notes>
			<Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">The DNS message parsing code in `named` includes a section whose computational complexity is overly high. It does not cause problems for typical DNS traffic, but crafted queries and responses may cause excessive CPU load on the affected `named` instance by exploiting this flaw. This issue affects both authoritative servers and recursive resolvers.
This issue affects BIND 9 versions 9.0.0 through 9.16.45, 9.18.0 through 9.18.21, 9.19.0 through 9.19.19, 9.9.3-S1 through 9.11.37-S1, 9.16.8-S1 through 9.16.45-S1, and 9.18.11-S1 through 9.18.21-S1.</Note>
		</Notes>
		<ReleaseDate>2024-03-22</ReleaseDate>
		<CVE>CVE-2023-4408</CVE>
		<ProductStatuses>
			<Status Type="Fixed">
				<ProductID>openEuler-22.03-LTS-SP1</ProductID>
			</Status>
		</ProductStatuses>
		<Threats>
			<Threat Type="Impact">
				<Description>High</Description>
			</Threat>
		</Threats>
		<CVSSScoreSets>
			<ScoreSet>
				<BaseScore>7.5</BaseScore>
				<Vector>AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H</Vector>
			</ScoreSet>
		</CVSSScoreSets>
		<Remediations>
			<Remediation Type="Vendor Fix">
				<Description>bind security update</Description>
				<DATE>2024-03-22</DATE>
				<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1324</URL>
			</Remediation>
		</Remediations>
	</Vulnerability>
	<Vulnerability Ordinal="2" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
		<Notes>
			<Note Title="Vulnerability Description" Type="General" Ordinal="2" xml:lang="en">Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote attackers to cause a denial of service (CPU consumption) via one or more DNSSEC responses, aka the &quot;KeyTrap&quot; issue. One of the concerns is that, when there is a zone with many DNSKEY and RRSIG records, the protocol specification implies that an algorithm must evaluate all combinations of DNSKEY and RRSIG records.</Note>
		</Notes>
		<ReleaseDate>2024-03-22</ReleaseDate>
		<CVE>CVE-2023-50387</CVE>
		<ProductStatuses>
			<Status Type="Fixed">
				<ProductID>openEuler-22.03-LTS-SP1</ProductID>
			</Status>
		</ProductStatuses>
		<Threats>
			<Threat Type="Impact">
				<Description>High</Description>
			</Threat>
		</Threats>
		<CVSSScoreSets>
			<ScoreSet>
				<BaseScore>7.5</BaseScore>
				<Vector>AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H</Vector>
			</ScoreSet>
		</CVSSScoreSets>
		<Remediations>
			<Remediation Type="Vendor Fix">
				<Description>bind security update</Description>
				<DATE>2024-03-22</DATE>
				<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1324</URL>
			</Remediation>
		</Remediations>
	</Vulnerability>
	<Vulnerability Ordinal="3" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
		<Notes>
			<Note Title="Vulnerability Description" Type="General" Ordinal="3" xml:lang="en">A flaw in query-handling code can cause `named` to exit prematurely with an assertion failure when:

  - `nxdomain-redirect &lt;domain&gt;;` is configured, and
  - the resolver receives a PTR query for an RFC 1918 address that would normally result in an authoritative NXDOMAIN response.
This issue affects BIND 9 versions 9.12.0 through 9.16.45, 9.18.0 through 9.18.21, 9.19.0 through 9.19.19, 9.16.8-S1 through 9.16.45-S1, and 9.18.11-S1 through 9.18.21-S1.</Note>
		</Notes>
		<ReleaseDate>2024-03-22</ReleaseDate>
		<CVE>CVE-2023-5517</CVE>
		<ProductStatuses>
			<Status Type="Fixed">
				<ProductID>openEuler-22.03-LTS-SP1</ProductID>
			</Status>
		</ProductStatuses>
		<Threats>
			<Threat Type="Impact">
				<Description>High</Description>
			</Threat>
		</Threats>
		<CVSSScoreSets>
			<ScoreSet>
				<BaseScore>7.5</BaseScore>
				<Vector>AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H</Vector>
			</ScoreSet>
		</CVSSScoreSets>
		<Remediations>
			<Remediation Type="Vendor Fix">
				<Description>bind security update</Description>
				<DATE>2024-03-22</DATE>
				<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1324</URL>
			</Remediation>
		</Remediations>
	</Vulnerability>
	<Vulnerability Ordinal="4" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
		<Notes>
			<Note Title="Vulnerability Description" Type="General" Ordinal="4" xml:lang="en">A bad interaction between DNS64 and serve-stale may cause `named` to crash with an assertion failure during recursive resolution, when both of these features are enabled.This issue affects BIND 9 versions 9.16.12 through 9.16.45, 9.18.0 through 9.18.21, 9.19.0 through 9.19.19, 9.16.12-S1 through 9.16.45-S1, and 9.18.11-S1 through 9.18.21-S1.</Note>
		</Notes>
		<ReleaseDate>2024-03-22</ReleaseDate>
		<CVE>CVE-2023-5679</CVE>
		<ProductStatuses>
			<Status Type="Fixed">
				<ProductID>openEuler-22.03-LTS-SP1</ProductID>
			</Status>
		</ProductStatuses>
		<Threats>
			<Threat Type="Impact">
				<Description>High</Description>
			</Threat>
		</Threats>
		<CVSSScoreSets>
			<ScoreSet>
				<BaseScore>7.5</BaseScore>
				<Vector>AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H</Vector>
			</ScoreSet>
		</CVSSScoreSets>
		<Remediations>
			<Remediation Type="Vendor Fix">
				<Description>bind security update</Description>
				<DATE>2024-03-22</DATE>
				<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1324</URL>
			</Remediation>
		</Remediations>
	</Vulnerability>
	<Vulnerability Ordinal="5" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
		<Notes>
			<Note Title="Vulnerability Description" Type="General" Ordinal="5" xml:lang="en">To keep its cache database efficient, `named` running as a recursive resolver occasionally attempts to clean up the database. It uses several methods, including some that are asynchronous: a small chunk of memory pointing to the cache element that can be cleaned up is first allocated and then queued for later processing. It was discovered that if the resolver is continuously processing query patterns triggering this type of cache-database maintenance, `named` may not be able to handle the cleanup events in a timely manner. This in turn enables the list of queued cleanup events to grow infinitely large over time, allowing the configured `max-cache-size` limit to be significantly exceeded.
This issue affects BIND 9 versions 9.16.0 through 9.16.45 and 9.16.8-S1 through 9.16.45-S1.</Note>
		</Notes>
		<ReleaseDate>2024-03-22</ReleaseDate>
		<CVE>CVE-2023-6516</CVE>
		<ProductStatuses>
			<Status Type="Fixed">
				<ProductID>openEuler-22.03-LTS-SP1</ProductID>
			</Status>
		</ProductStatuses>
		<Threats>
			<Threat Type="Impact">
				<Description>High</Description>
			</Threat>
		</Threats>
		<CVSSScoreSets>
			<ScoreSet>
				<BaseScore>7.5</BaseScore>
				<Vector>AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H</Vector>
			</ScoreSet>
		</CVSSScoreSets>
		<Remediations>
			<Remediation Type="Vendor Fix">
				<Description>bind security update</Description>
				<DATE>2024-03-22</DATE>
				<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1324</URL>
			</Remediation>
		</Remediations>
	</Vulnerability>
</cvrfdoc>