CVE-2022-21595

MariaDB is a multi-user, multi-threaded SQL database server that is binary compatible with MySQL.

The following packages have been upgraded to a later upstream version: galera (26.4.11), mariadb (10.5.16).

Security Fix(es):

• mariadb: MariaDB through 10.5.9 allows attackers to trigger a convert_const_to_int use-after-free when the BIGINT data type is used (CVE-2021-46669)

• mariadb: lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer (CVE-2022-24048)

• mariadb: lack of validating the existence of an object prior to performing operations on the object (CVE-2022-24050)

• mariadb: lack of proper validation of a user-supplied string before using it as a format specifier (CVE-2022-24051)

• mariadb: CONNECT Storage Engine Heap-based Buffer Overflow Privilege Escalation Vulnerability (CVE-2022-24052)

• mariadb: assertion failure in Item_args::walk_arg (CVE-2022-27376)

• mariadb: use-after-poison when complex conversion is involved in blob (CVE-2022-27377)

• mariadb: crash in create_tmp_table::finalize (CVE-2022-27378)

• mariadb: crash in component arg_comparator::compare_real_fixed (CVE-2022-27379)

• mariadb: crash at my_decimal::operator= (CVE-2022-27380)

• mariadb: crash at Field::set_default via specially crafted SQL statements (CVE-2022-27381)

• mariadb: assertion failure via component Item_field::used_tables/update_depend_map_for_order (CVE-2022-27382)

• mariadb: use-after-poison in my_strcasecmp_8bit() of ctype-simple.c (CVE-2022-27383)

• mariadb: via component Item_subselect::init_expr_cache_tracker (CVE-2022-27384)

• mariadb: crash in query_arena::set_query_arena upon SELECT from view (CVE-2022-27386)

• mariadb: assertion failures in decimal_bin_size (CVE-2022-27387)

• mariadb: crash when using HAVING with NOT EXIST predicate in an equality (CVE-2022-27444)

• mariadb: assertion failure in compare_order_elements (CVE-2022-27445)

• mariadb: crash when using HAVING with IS NULL predicate in an equality (CVE-2022-27446)

• mariadb: use-after-poison in Binary_string::free_buffer (CVE-2022-27447)

• mariadb: crash in multi-update and implicit grouping (CVE-2022-27448)

• mariadb: assertion failure in sql/item_func.cc (CVE-2022-27449)

• mariadb: crash via window function in expression in ORDER BY (CVE-2022-27451)

• mariadb: assertion failure in sql/item_cmpfunc.cc (CVE-2022-27452)

• mariadb: use-after-free when WHERE has subquery with an outer reference in HAVING (CVE-2022-27455)

• mariadb: assertion failure in VDec::VDec at /sql/sql_type.cc (CVE-2022-27456)

• mariadb: incorrect key in "dup value" error after long unique (CVE-2022-27457)

• mariadb: use-after-poison in Binary_string::free_buffer (CVE-2022-27458)

• mariadb: improper locking due to the unreleased lock in extra/mariabackup/ds_compress.cc (CVE-2022-31622)

• mariadb: improper locking due to the unreleased lock in extra/mariabackup/ds_compress.cc (CVE-2022-31623)

• mariadb: Crash executing query with VIEW, aggregate and subquery (CVE-2021-46659)

• mariadb: MariaDB allows an application crash in find_field_in_tables and find_order_in_list via an unused common table expression (CTE) (CVE-2021-46661)

• mariadb: MariaDB through 10.5.13 allows a ha_maria::extra application crash via certain SELECT statements (CVE-2021-46663)

• mariadb: crash in sub_select_postjoin_aggr for a NULL value of aggr (CVE-2021-46664)

• mariadb: crash because of incorrect used_tables expectations (CVE-2021-46665)

• mariadb: crash via certain long SELECT DISTINCT statements (CVE-2021-46668)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Bug Fix(es):

• Don't use less parallelism if not necessary (BZ#2096934)

• Links in galera package description are bad (BZ#2096935)

• [Tracker] Rebase to Galera 26.4.11 (BZ#2096936)

MariaDB is a multi-user, multi-threaded SQL database server that is binary compatible with MySQL.

The following packages have been upgraded to a later upstream version: galera (26.4.11), mariadb (10.5.16), mysql-selinux (1.0.5).

Security Fix(es):

• mariadb: MariaDB through 10.5.9 allows attackers to trigger a convert_const_to_int use-after-free when the BIGINT data type is used (CVE-2021-46669)

• mariadb: lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer (CVE-2022-24048)

• mariadb: lack of validating the existence of an object prior to performing operations on the object (CVE-2022-24050)

• mariadb: lack of proper validation of a user-supplied string before using it as a format specifier (CVE-2022-24051)

• mariadb: CONNECT Storage Engine Heap-based Buffer Overflow Privilege Escalation Vulnerability (CVE-2022-24052)

• mariadb: assertion failure in Item_args::walk_arg (CVE-2022-27376)

• mariadb: use-after-poison when complex conversion is involved in blob (CVE-2022-27377)

• mariadb: server crash in create_tmp_table::finalize (CVE-2022-27378)

• mariadb: server crash in component arg_comparator::compare_real_fixed (CVE-2022-27379)

• mariadb: server crash at my_decimal::operator= (CVE-2022-27380)

• mariadb: server crash at Field::set_default via specially crafted SQL statements (CVE-2022-27381)

• mariadb: assertion failure via component Item_field::used_tables/update_depend_map_for_order (CVE-2022-27382)

• mariadb: use-after-poison in my_strcasecmp_8bit() of ctype-simple.c (CVE-2022-27383)

• mariadb: crash via component Item_subselect::init_expr_cache_tracker (CVE-2022-27384)

• mariadb: server crashes in query_arena::set_query_arena upon SELECT from view (CVE-2022-27386)

• mariadb: assertion failures in decimal_bin_size (CVE-2022-27387)

• mariadb: crash when using HAVING with NOT EXIST predicate in an equality (CVE-2022-27444)

• mariadb: assertion failure in compare_order_elements (CVE-2022-27445)

• mariadb: crash when using HAVING with IS NULL predicate in an equality (CVE-2022-27446)

• mariadb: use-after-poison in Binary_string::free_buffer (CVE-2022-27447)

• mariadb: crash in multi-update and implicit grouping (CVE-2022-27448)

• mariadb: assertion failure in sql/item_func.cc (CVE-2022-27449)

• mariadb: crash via window function in expression in ORDER BY (CVE-2022-27451)

• mariadb: assertion failure in sql/item_cmpfunc.cc (CVE-2022-27452)

• mariadb: use-after-free when WHERE has subquery with an outer reference in HAVING (CVE-2022-27455)

• mariadb: assertion failure in VDec::VDec at /sql/sql_type.cc (CVE-2022-27456)

• mariadb: incorrect key in "dup value" error after long unique (CVE-2022-27457)

• mariadb: use-after-poison in Binary_string::free_buffer (CVE-2022-27458)

• mariadb: improper locking due to the unreleased lock in extra/mariabackup/ds_compress.cc (CVE-2022-31622)

• mariadb: improper locking due to the unreleased lock in extra/mariabackup/ds_compress.cc (CVE-2022-31623)

• mariadb: Crash executing query with VIEW, aggregate and subquery (CVE-2021-46659)

• mariadb: MariaDB allows an application crash in find_field_in_tables and find_order_in_list via an unused common table expression (CTE) (CVE-2021-46661)

• mariadb: MariaDB through 10.5.13 allows a ha_maria::extra application crash via certain SELECT statements (CVE-2021-46663)

• mariadb: MariaDB through 10.5.9 allows an application crash in sub_select_postjoin_aggr for a NULL value of aggr (CVE-2021-46664)

• mariadb: MariaDB through 10.5.9 allows a sql_parse.cc application crash because of incorrect used_tables expectations (CVE-2021-46665)

• mariadb: MariaDB through 10.5.9 allows an application crash via certain long SELECT DISTINCT statements (CVE-2021-46668)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

MariaDB is a multi-user, multi-threaded SQL database server that is binary compatible with MySQL.

The following packages have been upgraded to a later upstream version: mariadb (10.3.35), galera (25.3.35).

Security Fix(es):

• mariadb: MariaDB through 10.5.9 allows attackers to trigger a convert_const_to_int use-after-free when the BIGINT data type is used (CVE-2021-46669)

• mysql: Server: FTS unspecified vulnerability (CPU Apr 2022) (CVE-2022-21427)

• mariadb: lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer (CVE-2022-24048)

• mariadb: lack of validating the existence of an object prior to performing operations on the object (CVE-2022-24050)

• mariadb: lack of proper validation of a user-supplied string before using it as a format specifier (CVE-2022-24051)

• mariadb: CONNECT storage engine heap-based buffer overflow (CVE-2022-24052)

• mariadb: assertion failure in Item_args::walk_arg (CVE-2022-27376)

• mariadb: use-after-poison when complex conversion is involved in blob (CVE-2022-27377)

• mariadb: server crash in create_tmp_table::finalize (CVE-2022-27378)

• mariadb: server crash in component arg_comparator::compare_real_fixed (CVE-2022-27379)

• mariadb: server crash at my_decimal::operator= (CVE-2022-27380)

• mariadb: server crash at Field::set_default via specially crafted SQL statements (CVE-2022-27381)

• mariadb: use-after-poison in my_strcasecmp_8bit() of ctype-simple.c (CVE-2022-27383)

• mariadb: crash via component Item_subselect::init_expr_cache_tracker (CVE-2022-27384)

• mariadb: server crashes in query_arena::set_query_arena upon SELECT from view (CVE-2022-27386)

• mariadb: assertion failures in decimal_bin_size (CVE-2022-27387)

• mariadb: assertion failure in compare_order_elements (CVE-2022-27445)

• mariadb: use-after-poison in Binary_string::free_buffer (CVE-2022-27447)

• mariadb: crash in multi-update and implicit grouping (CVE-2022-27448)

• mariadb: assertion failure in sql/item_func.cc (CVE-2022-27449)

• mariadb: assertion failure in sql/item_cmpfunc.cc (CVE-2022-27452)

• mariadb: assertion failure in VDec::VDec at /sql/sql_type.cc (CVE-2022-27456)

• mariadb: use-after-poison in Binary_string::free_buffer (CVE-2022-27458)

• mariadb: improper locking due to the unreleased lock in extra/mariabackup/ds_compress.cc (CVE-2022-31622)

• mariadb: improper locking due to the unreleased lock in extra/mariabackup/ds_compress.cc (CVE-2022-31623)

• mariadb: server crash at Item_subselect::init_expr_cache_tracker (CVE-2022-32083)

• mariadb: server crash in Item_func_in::cleanup/Item::cleanup_processor (CVE-2022-32085)

• mariadb: server crash in Item_args::walk_args (CVE-2022-32087)

• mariadb: segmentation fault in Exec_time_tracker::get_loops/Filesort_tracker::report_use/filesort (CVE-2022-32088)

• mariadb: Crash executing query with VIEW, aggregate and subquery (CVE-2021-46659)

• mariadb: MariaDB allows an application crash in find_field_in_tables and find_order_in_list via an unused common table expression (CTE) (CVE-2021-46661)

• mariadb: MariaDB through 10.5.13 allows a ha_maria::extra application crash via certain SELECT statements (CVE-2021-46663)

• mariadb: MariaDB through 10.5.9 allows an application crash in sub_select_postjoin_aggr for a NULL value of aggr (CVE-2021-46664)

• mariadb: MariaDB through 10.5.9 allows a sql_parse.cc application crash because of incorrect used_tables expectations (CVE-2021-46665)

• mariadb: MariaDB through 10.5.9 allows an application crash via certain long SELECT DISTINCT statements (CVE-2021-46668)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Bug Fix(es):

• [Tracker] Rebase to Galera 25.3.35 for MariaDB-10.3 (BZ#2107075)

MySQL is a multi-user, multi-threaded SQL database server. It consists of the MySQL server daemon (mysqld) and many client programs and libraries.

The following packages have been upgraded to a later upstream version: mysql (8.0.30).

Security Fix(es):

• mysql: Server: DML multiple unspecified vulnerabilities (CVE-2021-2478, CVE-2021-2479, CVE-2021-35591, CVE-2021-35607, CVE-2022-21301, CVE-2022-21413)

• mysql: Server: Optimizer multiple unspecified vulnerabilities (CVE-2021-2481, CVE-2021-35575, CVE-2021-35577, CVE-2021-35610, CVE-2021-35612, CVE-2021-35626, CVE-2021-35627, CVE-2021-35628, CVE-2021-35634, CVE-2021-35635, CVE-2021-35636, CVE-2021-35638, CVE-2021-35641, CVE-2021-35642, CVE-2021-35643, CVE-2021-35644, CVE-2021-35645, CVE-2021-35646, CVE-2021-35647, CVE-2022-21253, CVE-2022-21254, CVE-2022-21264, CVE-2022-21278, CVE-2022-21297, CVE-2022-21339, CVE-2022-21342, CVE-2022-21351, CVE-2022-21370, CVE-2022-21378, CVE-2022-21412, CVE-2022-21414, CVE-2022-21435, CVE-2022-21436, CVE-2022-21437, CVE-2022-21438, CVE-2022-21440, CVE-2022-21452, CVE-2022-21459, CVE-2022-21462, CVE-2022-21478, CVE-2022-21479, CVE-2022-21509, CVE-2022-21525, CVE-2022-21526, CVE-2022-21527, CVE-2022-21528, CVE-2022-21529, CVE-2022-21530, CVE-2022-21531, CVE-2022-21553, CVE-2022-21569, CVE-2022-21265)

• mysql: Server: Replication multiple unspecified vulnerabilities (CVE-2021-35546, CVE-2022-21344, CVE-2022-21415)

• mysql: Server: Error Handling unspecified vulnerability (CVE-2021-35596)

• mysql: C API unspecified vulnerability (CVE-2021-35597)

• mysql: Server: Options multiple unspecified vulnerabilities (CVE-2021-35602, CVE-2021-35630, CVE-2022-21515)

• mysql: InnoDB multiple unspecified vulnerabilities (CVE-2021-35604, CVE-2022-21302, CVE-2022-21348, CVE-2022-21352, CVE-2022-21417, CVE-2022-21418, CVE-2022-21451, CVE-2022-21517, CVE-2022-21537, CVE-2022-21539, CVE-2022-21423)

• mysql: Server: Group Replication Plugin multiple unspecified vulnerabilities (CVE-2021-35608, CVE-2022-21256, CVE-2022-21379, CVE-2022-21454)

• mysql: Server: Security: Encryption multiple unspecified vulnerabilities (CVE-2021-35622, CVE-2022-21358, CVE-2022-21372, CVE-2022-21538)

• mysql: Server: Security: Privileges multiple unspecified vulnerabilities (CVE-2021-35624, CVE-2022-21245, CVE-2021-35625)

• mysql: Server: GIS unspecified vulnerability (CVE-2021-35631)

• mysql: Server: Data Dictionary unspecified vulnerability (CVE-2021-35632)

• mysql: Server: PS unspecified vulnerability (CVE-2021-35637)

• mysql: Server: Stored Procedure multiple unspecified vulnerabilities (CVE-2021-35639, CVE-2022-21303, CVE-2022-21522, CVE-2022-21534)

• mysql: Server: FTS multiple unspecified vulnerabilities (CVE-2021-35648, CVE-2022-21427)

• mysql: Server: Federated multiple unspecified vulnerabilities (CVE-2022-21270, CVE-2022-21547)

• mysql: Server: Parser unspecified vulnerability (CVE-2022-21304)

• mysql: Server: Information Schema multiple unspecified vulnerabilities (CVE-2022-21362, CVE-2022-21374)

• mysql: Server: Compiling unspecified vulnerability (CVE-2022-21367)

• mysql: Server: Components Services unspecified vulnerability (CVE-2022-21368)

• mysql: Server: DDL multiple unspecified vulnerabilities (CVE-2022-21425, CVE-2022-21444, CVE-2021-35640, CVE-2022-21249)

• mysql: Server: PAM Auth Plugin unspecified vulnerability (CVE-2022-21457)

• mysql: Server: Logging multiple unspecified vulnerabilities (CVE-2022-21460, CVE-2021-35633)

• mysql: Server: Security: Roles unspecified vulnerability (CVE-2021-35623)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Bug Fix(es):

• Rebuild mecab due to change in the suffix (from .el8 to .el8.0.0) [Rocky Linux-8] (BZ#2110940)

Vulnerability in the MySQL Server product of Oracle MySQL (component: C API). Supported versions that are affected are 5.7.36 and prior and 8.0.27 and prior. Difficult to exploit 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.4 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H).

MariaDB is a multi-user, multi-threaded SQL database server that is binary compatible with MySQL. The following packages have been upgraded to a later upstream version: galera (26.4.11), mariadb (10.5.16). Security Fix(es):

• mariadb: MariaDB through 10.5.9 allows attackers to trigger a convert_const_to_int use-after-free when the BIGINT data type is used (CVE-2021-46669)
• mariadb: lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer (CVE-2022-24048)
• mariadb: lack of validating the existence of an object prior to performing operations on the object (CVE-2022-24050)
• mariadb: lack of proper validation of a user-supplied string before using it as a format specifier (CVE-2022-24051)
• mariadb: CONNECT Storage Engine Heap-based Buffer Overflow Privilege Escalation Vulnerability (CVE-2022-24052)
• mariadb: assertion failure in Item_args::walk_arg (CVE-2022-27376)
• mariadb: use-after-poison when complex conversion is involved in blob (CVE-2022-27377)
• mariadb: crash in create_tmp_table::finalize (CVE-2022-27378)
• mariadb: crash in component arg_comparator::compare_real_fixed (CVE-2022-27379)
• mariadb: crash at my_decimal::operator= (CVE-2022-27380)
• mariadb: crash at Field::set_default via specially crafted SQL statements (CVE-2022-27381)
• mariadb: assertion failure via component Item_field::used_tables/update_depend_map_for_order (CVE-2022-27382)
• mariadb: use-after-poison in my_strcasecmp_8bit() of ctype-simple.c (CVE-2022-27383)
• mariadb: via component Item_subselect::init_expr_cache_tracker (CVE-2022-27384)
• mariadb: crash in query_arena::set_query_arena upon SELECT from view (CVE-2022-27386)
• mariadb: assertion failures in decimal_bin_size (CVE-2022-27387)
• mariadb: crash when using HAVING with NOT EXIST predicate in an equality (CVE-2022-27444)
• mariadb: assertion failure in compare_order_elements (CVE-2022-27445)
• mariadb: crash when using HAVING with IS NULL predicate in an equality (CVE-2022-27446)
• mariadb: use-after-poison in Binary_string::free_buffer (CVE-2022-27447)
• mariadb: crash in multi-update and implicit grouping (CVE-2022-27448)
• mariadb: assertion failure in sql/item_func.cc (CVE-2022-27449)
• mariadb: crash via window function in expression in ORDER BY (CVE-2022-27451)
• mariadb: assertion failure in sql/item_cmpfunc.cc (CVE-2022-27452)
• mariadb: use-after-free when WHERE has subquery with an outer reference in HAVING (CVE-2022-27455)
• mariadb: assertion failure in VDec::VDec at /sql/sql_type.cc (CVE-2022-27456)
• mariadb: incorrect key in "dup value" error after long unique (CVE-2022-27457)
• mariadb: use-after-poison in Binary_string::free_buffer (CVE-2022-27458)
• mariadb: improper locking due to the unreleased lock in extra/mariabackup/ds_compress.cc (CVE-2022-31622)
• mariadb: improper locking due to the unreleased lock in extra/mariabackup/ds_compress.cc (CVE-2022-31623)
• mariadb: Crash executing query with VIEW, aggregate and subquery (CVE-2021-46659)
• mariadb: MariaDB allows an application crash in find_field_in_tables and find_order_in_list via an unused common table expression (CTE) (CVE-2021-46661)
• mariadb: MariaDB through 10.5.13 allows a ha_maria::extra application crash via certain SELECT statements (CVE-2021-46663)
• mariadb: crash in sub_select_postjoin_aggr for a NULL value of aggr (CVE-2021-46664)
• mariadb: crash because of incorrect used_tables expectations (CVE-2021-46665)
• mariadb: crash via certain long SELECT DISTINCT statements (CVE-2021-46668) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section. Bug Fix(es):
• Don't use less parallelism if not necessary (BZ#2096934)
• Links in galera package description are bad (BZ#2096935)
• [Tracker] Rebase to Galera 26.4.11 (BZ#2096936)

MySQL is a multi-user, multi-threaded SQL database server. It consists of the MySQL server daemon (mysqld) and many client programs and libraries.

The following packages have been upgraded to a later upstream version: mysql (8.0.30).

Security Fix(es):

• mysql: Server: DML multiple unspecified vulnerabilities (CVE-2021-2478, CVE-2021-2479, CVE-2021-35591, CVE-2021-35607, CVE-2022-21301, CVE-2022-21413)
• mysql: Server: Optimizer multiple unspecified vulnerabilities (CVE-2021-2481, CVE-2021-35575, CVE-2021-35577, CVE-2021-35610, CVE-2021-35612, CVE-2021-35626, CVE-2021-35627, CVE-2021-35628, CVE-2021-35634, CVE-2021-35635, CVE-2021-35636, CVE-2021-35638, CVE-2021-35641, CVE-2021-35642, CVE-2021-35643, CVE-2021-35644, CVE-2021-35645, CVE-2021-35646, CVE-2021-35647, CVE-2022-21253, CVE-2022-21254, CVE-2022-21264, CVE-2022-21278, CVE-2022-21297, CVE-2022-21339, CVE-2022-21342, CVE-2022-21351, CVE-2022-21370, CVE-2022-21378, CVE-2022-21412, CVE-2022-21414, CVE-2022-21435, CVE-2022-21436, CVE-2022-21437, CVE-2022-21438, CVE-2022-21440, CVE-2022-21452, CVE-2022-21459, CVE-2022-21462, CVE-2022-21478, CVE-2022-21479, CVE-2022-21509, CVE-2022-21525, CVE-2022-21526, CVE-2022-21527, CVE-2022-21528, CVE-2022-21529, CVE-2022-21530, CVE-2022-21531, CVE-2022-21553, CVE-2022-21569, CVE-2022-21265)
• mysql: Server: Replication multiple unspecified vulnerabilities (CVE-2021-35546, CVE-2022-21344, CVE-2022-21415)
• mysql: Server: Error Handling unspecified vulnerability (CVE-2021-35596)
• mysql: C API unspecified vulnerability (CVE-2021-35597)
• mysql: Server: Options multiple unspecified vulnerabilities (CVE-2021-35602, CVE-2021-35630, CVE-2022-21515)
• mysql: InnoDB multiple unspecified vulnerabilities (CVE-2021-35604, CVE-2022-21302, CVE-2022-21348, CVE-2022-21352, CVE-2022-21417, CVE-2022-21418, CVE-2022-21451, CVE-2022-21517, CVE-2022-21537, CVE-2022-21539, CVE-2022-21423)
• mysql: Server: Group Replication Plugin multiple unspecified vulnerabilities (CVE-2021-35608, CVE-2022-21256, CVE-2022-21379, CVE-2022-21454)
• mysql: Server: Security: Encryption multiple unspecified vulnerabilities (CVE-2021-35622, CVE-2022-21358, CVE-2022-21372, CVE-2022-21538)
• mysql: Server: Security: Privileges multiple unspecified vulnerabilities (CVE-2021-35624, CVE-2022-21245, CVE-2021-35625)
• mysql: Server: GIS unspecified vulnerability (CVE-2021-35631)
• mysql: Server: Data Dictionary unspecified vulnerability (CVE-2021-35632)
• mysql: Server: PS unspecified vulnerability (CVE-2021-35637)
• mysql: Server: Stored Procedure multiple unspecified vulnerabilities (CVE-2021-35639, CVE-2022-21303, CVE-2022-21522, CVE-2022-21534)
• mysql: Server: FTS multiple unspecified vulnerabilities (CVE-2021-35648, CVE-2022-21427)
• mysql: Server: Federated multiple unspecified vulnerabilities (CVE-2022-21270, CVE-2022-21547)
• mysql: Server: Parser unspecified vulnerability (CVE-2022-21304)
• mysql: Server: Information Schema multiple unspecified vulnerabilities (CVE-2022-21362, CVE-2022-21374)
• mysql: Server: Compiling unspecified vulnerability (CVE-2022-21367)
• mysql: Server: Components Services unspecified vulnerability (CVE-2022-21368)
• mysql: Server: DDL multiple unspecified vulnerabilities (CVE-2022-21425, CVE-2022-21444, CVE-2021-35640, CVE-2022-21249)
• mysql: Server: PAM Auth Plugin unspecified vulnerability (CVE-2022-21457)
• mysql: Server: Logging multiple unspecified vulnerabilities (CVE-2022-21460, CVE-2021-35633)
• mysql: Server: Security: Roles unspecified vulnerability (CVE-2021-35623)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Bug Fix(es):

• Rebuild mecab due to change in the suffix (from .el8 to .el8.0.0) [almalinux-8] (BZ#2110940)

Vulnerability in the MySQL Server product of Oracle MySQL (component: C API). Supported versions that are affected are 5.7.36 and prior and 8.0.27 and prior. Difficult to exploit 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.4 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H).

Vulnerability in the MySQL Server product of Oracle MySQL (component: C API). Supported versions that are affected are 5.7.36 and prior and 8.0.27 and prior. Difficult to exploit 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.4 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H).

Vulnerability in the MySQL Server product of Oracle MySQL (component: C API). Supported versions that are affected are 5.7.36 and prior and 8.0.27 and prior. Difficult to exploit 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.4 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H).

This update for mariadb104 fixes the following issues:

• Implement version 10.4 of MariaDB (jsc#PED-2455):
  • It is possible to use more than one authentication plugin for each user account.
  • The root user account is being created with the ability to use two authentication plugins.
  • All user accounts, passwords, and global privileges are now stored in the mysql.global_priv table.
  • Is being supported for User Password Expiry, which is not active by default.
  • Faster privilege checks for MariaDB setups with many user accounts or many database grants.
• Update mysql-systemd-helper to be aware of custom group (bsc#1200105)
• MariaDB is now support lz4 compression for 'INNODB'. (bsc#1186031)
• Add 'mysql-user.conf' file to enable systemd generating mysql user in containers. (bsc#1173028)
• Fixes an issue when MariaDB is ignoring the value of the parameter 'open_files_limit' in the global variables. (bsc#1180014)

This update for mariadb104 fixes the following issues:

• Implement version 10.4 of MariaDB (jsc#PED-2455):
  • It is possible to use more than one authentication plugin for each user account.
  • The root user account is being created with the ability to use two authentication plugins.
  • All user accounts, passwords, and global privileges are now stored in the mysql.global_priv table.
  • Is being supported for User Password Expiry, which is not active by default.
  • Faster privilege checks for MariaDB setups with many user accounts or many database grants.
• Update mysql-systemd-helper to be aware of custom group (bsc#1200105)
• MariaDB is now support lz4 compression for 'INNODB'. (bsc#1186031)
• Add 'mysql-user.conf' file to enable systemd generating mysql user in containers. (bsc#1173028)
• Fixes an issue when MariaDB is ignoring the value of the parameter 'open_files_limit' in the global variables. (bsc#1180014)

This update for mariadb fixes the following issues:

• CVE-2022-38791: Fixed deadlock in compress_write in extra/mariabackup/ds_compress.cc (bsc#1202863).

Version update from 10.4.26 to 10.4.28 (fixes CVE-2022-38791 and CVE-2022-38791).

• Update to 10.4.28:

  • https://mariadb.com/kb/en/library/mariadb-10428-release-notes
  • https://mariadb.com/kb/en/library/mariadb-10428-changelog
  • https://mariadb.com/kb/en/library/mariadb-10427-release-notes
  • https://mariadb.com/kb/en/library/mariadb-10427-changelog

• Update list of skipped tests

• Update mariadb.keyring