<?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 mysql 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-2072</ID>
		</Identification>
		<Status>Final</Status>
		<Version>1.0</Version>
		<RevisionHistory>
			<Revision>
				<Number>1.0</Number>
				<Date>2024-08-30</Date>
				<Description>Initial</Description>
			</Revision>
		</RevisionHistory>
		<InitialReleaseDate>2024-08-30</InitialReleaseDate>
		<CurrentReleaseDate>2024-08-30</CurrentReleaseDate>
		<Generator>
			<Engine>openEuler SA Tool V1.0</Engine>
			<Date>2024-08-30</Date>
		</Generator>
	</DocumentTracking>
	<DocumentNotes>
		<Note Title="Synopsis" Type="General" Ordinal="1" xml:lang="en">mysql security update</Note>
		<Note Title="Summary" Type="General" Ordinal="2" xml:lang="en">An update for mysql is now available for openEuler-22.03-LTS-SP1</Note>
		<Note Title="Description" Type="General" Ordinal="3" xml:lang="en">The MySQL(TM) software delivers a very fast, multi-threaded, multi-user, and robust SQL (Structured Query Language) database server. MySQL Server is intended for mission-critical, heavy-load production systems as well as for embedding into mass-deployed software. MySQL is a trademark of Oracle and/or its affiliates

Security Fix(es):

The public API function BIO_new_NDEF is a helper function used for streaming
ASN.1 data via a BIO. It is primarily used internally to OpenSSL to support the
SMIME, CMS and PKCS7 streaming capabilities, but may also be called directly by
end user applications.

The function receives a BIO from the caller, prepends a new BIO_f_asn1 filter
BIO onto the front of it to form a BIO chain, and then returns the new head of
the BIO chain to the caller. Under certain conditions, for example if a CMS
recipient public key is invalid, the new filter BIO is freed and the function
returns a NULL result indicating a failure. However, in this case, the BIO chain
is not properly cleaned up and the BIO passed by the caller still retains
internal pointers to the previously freed filter BIO. If the caller then goes on
to call BIO_pop() on the BIO then a use-after-free will occur. This will most
likely result in a crash.



This scenario occurs directly in the internal function B64_write_ASN1() which
may cause BIO_new_NDEF() to be called and will subsequently call BIO_pop() on
the BIO. This internal function is in turn called by the public API functions
PEM_write_bio_ASN1_stream, PEM_write_bio_CMS_stream, PEM_write_bio_PKCS7_stream,
SMIME_write_ASN1, SMIME_write_CMS and SMIME_write_PKCS7.

Other public API functions that may be impacted by this include
i2d_ASN1_bio_stream, BIO_new_CMS, BIO_new_PKCS7, i2d_CMS_bio_stream and
i2d_PKCS7_bio_stream.

The OpenSSL cms and smime command line applications are similarly affected.



(CVE-2023-0215)

This flaw makes curl overflow a heap based buffer in the SOCKS5 proxy
handshake.

When curl is asked to pass along the host name to the SOCKS5 proxy to allow
that to resolve the address instead of it getting done by curl itself, the
maximum length that host name can be is 255 bytes.

If the host name is detected to be longer, curl switches to local name
resolving and instead passes on the resolved address only. Due to this bug,
the local variable that means &quot;let the host resolve the name&quot; could get the
wrong value during a slow SOCKS5 handshake, and contrary to the intention,
copy the too long host name to the target buffer instead of copying just the
resolved address there.

The target buffer being a heap based buffer, and the host name coming from the
URL that curl has been told to operate with.
(CVE-2023-38545)

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer).  Supported versions that are affected are 8.0.35 and prior and  8.2.0 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server.  Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).(CVE-2024-21137)

Vulnerability in the MySQL Server product of Oracle MySQL (component: InnoDB).  Supported versions that are affected are 8.0.36 and prior and  8.3.0 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server.  Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).(CVE-2024-21159)</Note>
		<Note Title="Topic" Type="General" Ordinal="4" xml:lang="en">An update for mysql 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">mysql</Note>
	</DocumentNotes>
	<DocumentReferences>
		<Reference Type="Self">
			<URL>https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2072</URL>
		</Reference>
		<Reference Type="openEuler CVE">
			<URL>https://www.openeuler.org/en/security/cve/detail/?cveId=CVE-2023-0215</URL>
			<URL>https://www.openeuler.org/en/security/cve/detail/?cveId=CVE-2023-38545</URL>
			<URL>https://www.openeuler.org/en/security/cve/detail/?cveId=CVE-2024-21137</URL>
			<URL>https://www.openeuler.org/en/security/cve/detail/?cveId=CVE-2024-21159</URL>
		</Reference>
		<Reference Type="Other">
			<URL>https://nvd.nist.gov/vuln/detail/CVE-2023-0215</URL>
			<URL>https://nvd.nist.gov/vuln/detail/CVE-2023-38545</URL>
			<URL>https://nvd.nist.gov/vuln/detail/CVE-2024-21137</URL>
			<URL>https://nvd.nist.gov/vuln/detail/CVE-2024-21159</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="mysql-8.0.38-1" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">mysql-8.0.38-1.oe2203sp1.aarch64.rpm</FullProductName>
			<FullProductName ProductID="mysql-common-8.0.38-1" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">mysql-common-8.0.38-1.oe2203sp1.aarch64.rpm</FullProductName>
			<FullProductName ProductID="mysql-config-8.0.38-1" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">mysql-config-8.0.38-1.oe2203sp1.aarch64.rpm</FullProductName>
			<FullProductName ProductID="mysql-debuginfo-8.0.38-1" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">mysql-debuginfo-8.0.38-1.oe2203sp1.aarch64.rpm</FullProductName>
			<FullProductName ProductID="mysql-debugsource-8.0.38-1" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">mysql-debugsource-8.0.38-1.oe2203sp1.aarch64.rpm</FullProductName>
			<FullProductName ProductID="mysql-devel-8.0.38-1" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">mysql-devel-8.0.38-1.oe2203sp1.aarch64.rpm</FullProductName>
			<FullProductName ProductID="mysql-errmsg-8.0.38-1" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">mysql-errmsg-8.0.38-1.oe2203sp1.aarch64.rpm</FullProductName>
			<FullProductName ProductID="mysql-help-8.0.38-1" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">mysql-help-8.0.38-1.oe2203sp1.aarch64.rpm</FullProductName>
			<FullProductName ProductID="mysql-libs-8.0.38-1" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">mysql-libs-8.0.38-1.oe2203sp1.aarch64.rpm</FullProductName>
			<FullProductName ProductID="mysql-server-8.0.38-1" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">mysql-server-8.0.38-1.oe2203sp1.aarch64.rpm</FullProductName>
			<FullProductName ProductID="mysql-test-8.0.38-1" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">mysql-test-8.0.38-1.oe2203sp1.aarch64.rpm</FullProductName>
		</Branch>
		<Branch Type="Package Arch" Name="src">
			<FullProductName ProductID="mysql-8.0.38-1" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">mysql-8.0.38-1.oe2203sp1.src.rpm</FullProductName>
		</Branch>
		<Branch Type="Package Arch" Name="x86_64">
			<FullProductName ProductID="mysql-8.0.38-1" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">mysql-8.0.38-1.oe2203sp1.x86_64.rpm</FullProductName>
			<FullProductName ProductID="mysql-common-8.0.38-1" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">mysql-common-8.0.38-1.oe2203sp1.x86_64.rpm</FullProductName>
			<FullProductName ProductID="mysql-config-8.0.38-1" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">mysql-config-8.0.38-1.oe2203sp1.x86_64.rpm</FullProductName>
			<FullProductName ProductID="mysql-debuginfo-8.0.38-1" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">mysql-debuginfo-8.0.38-1.oe2203sp1.x86_64.rpm</FullProductName>
			<FullProductName ProductID="mysql-debugsource-8.0.38-1" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">mysql-debugsource-8.0.38-1.oe2203sp1.x86_64.rpm</FullProductName>
			<FullProductName ProductID="mysql-devel-8.0.38-1" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">mysql-devel-8.0.38-1.oe2203sp1.x86_64.rpm</FullProductName>
			<FullProductName ProductID="mysql-errmsg-8.0.38-1" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">mysql-errmsg-8.0.38-1.oe2203sp1.x86_64.rpm</FullProductName>
			<FullProductName ProductID="mysql-help-8.0.38-1" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">mysql-help-8.0.38-1.oe2203sp1.x86_64.rpm</FullProductName>
			<FullProductName ProductID="mysql-libs-8.0.38-1" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">mysql-libs-8.0.38-1.oe2203sp1.x86_64.rpm</FullProductName>
			<FullProductName ProductID="mysql-server-8.0.38-1" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">mysql-server-8.0.38-1.oe2203sp1.x86_64.rpm</FullProductName>
			<FullProductName ProductID="mysql-test-8.0.38-1" CPE="cpe:/a:openEuler:openEuler:22.03-LTS-SP1">mysql-test-8.0.38-1.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 public API function BIO_new_NDEF is a helper function used for streamingASN.1 data via a BIO. It is primarily used internally to OpenSSL to support theSMIME, CMS and PKCS7 streaming capabilities, but may also be called directly byend user applications.The function receives a BIO from the caller, prepends a new BIO_f_asn1 filterBIO onto the front of it to form a BIO chain, and then returns the new head ofthe BIO chain to the caller. Under certain conditions, for example if a CMSrecipient public key is invalid, the new filter BIO is freed and the functionreturns a NULL result indicating a failure. However, in this case, the BIO chainis not properly cleaned up and the BIO passed by the caller still retainsinternal pointers to the previously freed filter BIO. If the caller then goes onto call BIO_pop() on the BIO then a use-after-free will occur. This will mostlikely result in a crash.This scenario occurs directly in the internal function B64_write_ASN1() whichmay cause BIO_new_NDEF() to be called and will subsequently call BIO_pop() onthe BIO. This internal function is in turn called by the public API functionsPEM_write_bio_ASN1_stream, PEM_write_bio_CMS_stream, PEM_write_bio_PKCS7_stream,SMIME_write_ASN1, SMIME_write_CMS and SMIME_write_PKCS7.Other public API functions that may be impacted by this includei2d_ASN1_bio_stream, BIO_new_CMS, BIO_new_PKCS7, i2d_CMS_bio_stream andi2d_PKCS7_bio_stream.The OpenSSL cms and smime command line applications are similarly affected.</Note>
		</Notes>
		<ReleaseDate>2024-08-30</ReleaseDate>
		<CVE>CVE-2023-0215</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>mysql security update</Description>
				<DATE>2024-08-30</DATE>
				<URL>https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2072</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="1" xml:lang="en">This flaw makes curl overflow a heap based buffer in the SOCKS5 proxyhandshake.When curl is asked to pass along the host name to the SOCKS5 proxy to allowthat to resolve the address instead of it getting done by curl itself, themaximum length that host name can be is 255 bytes.If the host name is detected to be longer, curl switches to local nameresolving and instead passes on the resolved address only. Due to this bug,the local variable that means  let the host resolve the name  could get thewrong value during a slow SOCKS5 handshake, and contrary to the intention,copy the too long host name to the target buffer instead of copying just theresolved address there.The target buffer being a heap based buffer, and the host name coming from theURL that curl has been told to operate with.</Note>
		</Notes>
		<ReleaseDate>2024-08-30</ReleaseDate>
		<CVE>CVE-2023-38545</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:H/PR:N/UI:R/S:U/C:H/I:H/A:H</Vector>
			</ScoreSet>
		</CVSSScoreSets>
		<Remediations>
			<Remediation Type="Vendor Fix">
				<Description>mysql security update</Description>
				<DATE>2024-08-30</DATE>
				<URL>https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2072</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="1" xml:lang="en">Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer).  Supported versions that are affected are 8.0.35 and prior and  8.2.0 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server.  Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).</Note>
		</Notes>
		<ReleaseDate>2024-08-30</ReleaseDate>
		<CVE>CVE-2024-21137</CVE>
		<ProductStatuses>
			<Status Type="Fixed">
				<ProductID>openEuler-22.03-LTS-SP1</ProductID>
			</Status>
		</ProductStatuses>
		<Threats>
			<Threat Type="Impact">
				<Description>Medium</Description>
			</Threat>
		</Threats>
		<CVSSScoreSets>
			<ScoreSet>
				<BaseScore>4.9</BaseScore>
				<Vector>AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H</Vector>
			</ScoreSet>
		</CVSSScoreSets>
		<Remediations>
			<Remediation Type="Vendor Fix">
				<Description>mysql security update</Description>
				<DATE>2024-08-30</DATE>
				<URL>https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2072</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="1" xml:lang="en">Vulnerability in the MySQL Server product of Oracle MySQL (component: InnoDB).  Supported versions that are affected are 8.0.36 and prior and  8.3.0 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server.  Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).</Note>
		</Notes>
		<ReleaseDate>2024-08-30</ReleaseDate>
		<CVE>CVE-2024-21159</CVE>
		<ProductStatuses>
			<Status Type="Fixed">
				<ProductID>openEuler-22.03-LTS-SP1</ProductID>
			</Status>
		</ProductStatuses>
		<Threats>
			<Threat Type="Impact">
				<Description>Medium</Description>
			</Threat>
		</Threats>
		<CVSSScoreSets>
			<ScoreSet>
				<BaseScore>4.9</BaseScore>
				<Vector>AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H</Vector>
			</ScoreSet>
		</CVSSScoreSets>
		<Remediations>
			<Remediation Type="Vendor Fix">
				<Description>mysql security update</Description>
				<DATE>2024-08-30</DATE>
				<URL>https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2072</URL>
			</Remediation>
		</Remediations>
	</Vulnerability>
</cvrfdoc>