CVE-2022-27378

An issue in the component Create_tmp_table::finalize of MariaDB Server v10.7 and below was discovered to allow attackers to cause a Denial of Service (DoS) via specially crafted SQL statements.

MariaDB is a community developed fork from MySQL - a multi-user, multi-threaded SQL database server. It is a client/server implementation consisting of a server daemon (mariadbd) and many different client programs and libraries. The base package contains the standard MariaDB/MySQL client programs and utilities.

Security Fix(es):

An issue in the component Arg_comparator::compare_real_fixed of MariaDB Server v10.6.2 and below was discovered to allow attackers to cause a Denial of Service (DoS) via specially crafted SQL statements.(CVE-2022-27379)

MariaDB Server v10.7 and below was discovered to contain a segmentation fault via the component sql/sql_class.cc.(CVE-2022-27386)

MariaDB Server v10.7 and below was discovered to contain a global buffer overflow in the component decimal_bin_size, which is exploited via specially crafted SQL statements.(CVE-2022-27387)

An issue in the component Item_subselect::init_expr_cache_tracker of MariaDB Server v10.6 and below was discovered to allow attackers to cause a Denial of Service (DoS) via specially crafted SQL statements.(CVE-2022-27384)

An issue in the component my_decimal::operator= of MariaDB Server v10.6.3 and below was discovered to allow attackers to cause a Denial of Service (DoS) via specially crafted SQL statements.(CVE-2022-27380)

MariaDB Server v10.6 and below was discovered to contain an use-after-free in the component my_strcasecmp_8bit, which is exploited via specially crafted SQL statements.(CVE-2022-27383)

An issue in the component Field::set_default of MariaDB Server v10.6 and below was discovered to allow attackers to cause a Denial of Service (DoS) via specially crafted SQL statements.(CVE-2022-27381)

MariaDB Server v10.6.3 and below was discovered to contain an use-after-free in the component Item_func_in::cleanup(), which is exploited via specially crafted SQL statements.(CVE-2022-27377)

An issue in the component Create_tmp_table::finalize of MariaDB Server v10.7 and below was discovered to allow attackers to cause a Denial of Service (DoS) via specially crafted SQL statements.(CVE-2022-27378)

MariaDB Server v10.6.5 and below was discovered to contain an use-after-free in the component Item_args::walk_arg, which is exploited via specially crafted SQL statements.(CVE-2022-27376)

MariaDB Server v10.9 and below was discovered to contain a segmentation fault via the component sql/item_cmpfunc.cc.(CVE-2022-27452)

MariaDB Server v10.6.3 and below was discovered to contain an use-after-free in the component Binary_string::free_buffer() at /sql/sql_string.h.(CVE-2022-27458)

MariaDB Server v10.6.3 and below was discovered to contain an use-after-free in the component VDec::VDec at /sql/sql_type.cc.(CVE-2022-27456)

MariaDB Server v10.9 and below was discovered to contain a segmentation fault via the component sql/sql_window.cc.(CVE-2022-27445)

MariaDB Server v10.9 and below was discovered to contain a segmentation fault via the component sql/item_func.cc:148.(CVE-2022-27449)

There is an Assertion failure in MariaDB Server v10.9 and below via 'node->pcur->rel_pos == BTR_PCUR_ON' at /row/row0mysql.cc.(CVE-2022-27448)

MariaDB Server v10.9 and below was discovered to contain a use-after-free via the component Binary_string::free_buffer() at /sql/sql_string.h.(CVE-2022-27447)

An issue in the component Used_tables_and_const_cache::used_tables_and_const_cache_join of MariaDB Server v10.7 and below was discovered to allow attackers to cause a Denial of Service (DoS) via specially crafted SQL statements.(CVE-2022-27385)

MariaDB Server v10.7 and below was discovered to contain a segmentation fault via the component Item_field::used_tables/update_depend_map_for_order.(CVE-2022-27382)

MariaDB Server v10.9 and below was discovered to contain a segmentation fault via the component sql/field_conv.cc.(CVE-2022-27451)

MariaDB Server v10.6.3 and below was discovered to contain an use-after-free in the component my_mb_wc_latin1 at…

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)

An issue in the component Create_tmp_table::finalize of MariaDB Server v10.7 and below was discovered to allow attackers to cause a Denial of Service (DoS) via specially crafted SQL statements.

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)

An issue in the component Create_tmp_table::finalize of MariaDB Server v10.7 and below was discovered to allow attackers to cause a Denial of Service (DoS) via specially crafted SQL statements.

An issue in the component Create_tmp_table::finalize of MariaDB Server v10.7 and below was discovered to allow attackers to cause a Denial of Service (DoS) via specially crafted SQL statements.

An issue in the component Create_tmp_table::finalize of MariaDB Server v10.7 and below was discovered to allow attackers to cause a Denial of Service (DoS) via specially crafted SQL statements.

An issue in the component Create_tmp_table::finalize of MariaDB Server v10.7 and below was discovered to allow attackers to cause a Denial of Service (DoS) via specially crafted SQL statements.

Some security vulenarbilities have been fixed. Some bigger bugs in optimizer and replication engine have been found and fixed. See release notes for details.

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:

Update to 10.5.16 (bsc#1199928):

• CVE-2021-46669 (bsc#1199928)

• CVE-2022-27376 (bsc#1198628)

• CVE-2022-27377 (bsc#1198603)

• CVE-2022-27378 (bsc#1198604)

• CVE-2022-27379 (bsc#1198605)

• CVE-2022-27380 (bsc#1198606)

• CVE-2022-27381 (bsc#1198607)

• CVE-2022-27382 (bsc#1198609)

• CVE-2022-27383 (bsc#1198610)

• CVE-2022-27384 (bsc#1198611)

• CVE-2022-27386 (bsc#1198612)

• CVE-2022-27387 (bsc#1198613)

• CVE-2022-27444 (bsc#1198634)

• CVE-2022-27445 (bsc#1198629)

• CVE-2022-27446 (bsc#1198630)

• CVE-2022-27447 (bsc#1198631)

• CVE-2022-27448 (bsc#1198632)

• CVE-2022-27449 (bsc#1198633)

• CVE-2022-27451 (bsc#1198639)

• CVE-2022-27452 (bsc#1198640)

• CVE-2022-27455 (bsc#1198638)

• CVE-2022-27456 (bsc#1198635)

• CVE-2022-27457 (bsc#1198636)

• CVE-2022-27458 (bsc#1198637)

• The following issue is not affecting this package: CVE-2022-21427

External refernences:

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

This update for mariadb fixes the following issues:

• CVE-2021-46669 (bsc#1199928)
• CVE-2022-21427 (bsc#1199928)
• CVE-2022-27377 (bsc#1198603)
• CVE-2022-27378 (bsc#1198604)
• CVE-2022-27380 (bsc#1198606)
• CVE-2022-27381 (bsc#1198607)
• CVE-2022-27383 (bsc#1198610)
• CVE-2022-27384 (bsc#1198611)
• CVE-2022-27386 (bsc#1198612)
• CVE-2022-27387 (bsc#1198613)
• CVE-2022-27445 (bsc#1198629)

This update for mariadb fixes the following issues:

• CVE-2021-46669 (bsc#1199928)
• CVE-2022-21427 (bsc#1199928)
• CVE-2022-27377 (bsc#1198603)
• CVE-2022-27378 (bsc#1198604)
• CVE-2022-27380 (bsc#1198606)
• CVE-2022-27381 (bsc#1198607)
• CVE-2022-27383 (bsc#1198610)
• CVE-2022-27384 (bsc#1198611)
• CVE-2022-27386 (bsc#1198612)
• CVE-2022-27387 (bsc#1198613)
• CVE-2022-27445 (bsc#1198629)

This update for mariadb fixes the following issues:

Update to 10.4.25 (bsc#1199928):

• CVE-2021-46669 (bsc#1199928)
• CVE-2022-21427 (bsc#1199928)
• CVE-2022-27376 (bsc#1198628)
• CVE-2022-27377 (bsc#1198603)
• CVE-2022-27378 (bsc#1198604)
• CVE-2022-27379 (bsc#1198605)
• CVE-2022-27380 (bsc#1198606)
• CVE-2022-27381 (bsc#1198607)
• CVE-2022-27382 (bsc#1198609)
• CVE-2022-27383 (bsc#1198610)
• CVE-2022-27384 (bsc#1198611)
• CVE-2022-27386 (bsc#1198612)
• CVE-2022-27387 (bsc#1198613)
• CVE-2022-27444 (bsc#1198634)
• CVE-2022-27445 (bsc#1198629)
• CVE-2022-27446 (bsc#1198630)
• CVE-2022-27447 (bsc#1198631)
• CVE-2022-27448 (bsc#1198632)
• CVE-2022-27449 (bsc#1198633)
• CVE-2022-27451 (bsc#1198639)
• CVE-2022-27452 (bsc#1198640)
• CVE-2022-27455 (bsc#1198638)
• CVE-2022-27456 (bsc#1198635)
• CVE-2022-27457 (bsc#1198636)
• CVE-2022-27458 (bsc#1198637)

External refernences:

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

This update for mariadb fixes the following issues:

• Added mariadb-galera (jsc#SLE-22245)

Update to 10.6.8 (bsc#1199928):

• CVE-2021-46669 (bsc#1199928)

• CVE-2022-27376 (bsc#1198628)

• CVE-2022-27377 (bsc#1198603)

• CVE-2022-27378 (bsc#1198604)

• CVE-2022-27379 (bsc#1198605)

• CVE-2022-27380 (bsc#1198606)

• CVE-2022-27381 (bsc#1198607)

• CVE-2022-27382 (bsc#1198609)

• CVE-2022-27383 (bsc#1198610)

• CVE-2022-27384 (bsc#1198611)

• CVE-2022-27386 (bsc#1198612)

• CVE-2022-27387 (bsc#1198613)

• CVE-2022-27444 (bsc#1198634)

• CVE-2022-27445 (bsc#1198629)

• CVE-2022-27446 (bsc#1198630)

• CVE-2022-27447 (bsc#1198631)

• CVE-2022-27448 (bsc#1198632)

• CVE-2022-27449 (bsc#1198633)

• CVE-2022-27451 (bsc#1198639)

• CVE-2022-27452 (bsc#1198640)

• CVE-2022-27455 (bsc#1198638)

• CVE-2022-27456 (bsc#1198635)

• CVE-2022-27457 (bsc#1198636)

• CVE-2022-27458 (bsc#1198637)

• The following issue is not affecting this package: CVE-2022-21427

Update to 10.6.7 (bsc#1196016):

• CVE-2021-46665, CVE-2021-46664, CVE-2021-46661, CVE-2021-46668, CVE-2021-46663

Update to 10.6.6:

• CVE-2022-24052, CVE-2022-24051, CVE-2022-24050, CVE-2022-24048, CVE-2021-46659 (bsc#1195339)

The following issues have been fixed already but didn't have CVE references:

• CVE-2021-46658 (bsc#1195334)
• CVE-2021-46657 (bsc#1195325)

Non security fixes:

• Skip failing tests for s390x, fixes bsc#1195076

External refernences:

• https://mariadb.com/kb/en/library/mariadb-1068-release-notes
• https://mariadb.com/kb/en/library/mariadb-1068-changelog
• https://mariadb.com/kb/en/library/mariadb-1067-release-notes
• https://mariadb.com/kb/en/library/mariadb-1067-changelog
• https://mariadb.com/kb/en/library/mariadb-1066-release-notes
• https://mariadb.com/kb/en/library/mariadb-1066-changelog

Several security issues were discovered in MariaDB and this update includes new upstream MariaDB versions to fix these issues.

MariaDB has been updated to 10.3.37 in Ubuntu 20.04 LTS and to 10.6.11 in Ubuntu 22.04 LTS and Ubuntu 22.10.

In addition to security fixes, the updated packages contain bug fixes, new features, and possibly incompatible changes.