13 matches found
BIT-MYSQL-CLIENT-2022-32086
MariaDB v10.4 to v10.8 was discovered to contain a segmentation fault via the component Itemfield::fixouterfield...
BIT-MARIADB-2022-32086
MariaDB v10.4 to v10.8 was discovered to contain a segmentation fault via the component Itemfield::fixouterfield...
BIT-2022-32086
MariaDB v10.4 to v10.8 was discovered to contain a segmentation fault via the component Itemfield::fixouterfield...
SUSE CVE-2022-32086
MariaDB v10.4 to v10.8 was discovered to contain a segmentation fault via the component Itemfield::fixouterfield...
mariadb: server crash in Item_field::fix_outer_field for INSERT SELECT
MariaDB v10.4 to v10.8 was discovered to contain a segmentation fault via the component Itemfield::fixouterfield...
mariadb: server crash in Item_field::fix_outer_field for INSERT SELECT
MariaDB v10.4 to v10.8 was discovered to contain a segmentation fault via the component Itemfield::fixouterfield...
mariadb: server crash in Item_field::fix_outer_field for INSERT SELECT
MariaDB v10.4 to v10.8 was discovered to contain a segmentation fault via the component Itemfield::fixouterfield...
CVE-2022-32086
MariaDB v10.4 to v10.8 was discovered to contain a segmentation fault via the component Itemfield::fixouterfield...
Design/Logic Flaw
MariaDB v10.4 to v10.8 was discovered to contain a segmentation fault via the component Itemfield::fixouterfield...
CVE-2022-32086
MariaDB v10.4 to v10.8 was discovered to contain a segmentation fault via the component Itemfield::fixouterfield...
CVE-2022-32086
MariaDB v10.4 to v10.8 was discovered to contain a segmentation fault via the component Itemfield::fixouterfield...
CVE-2022-32086
MariaDB v10.4 to v10.8 was discovered to contain a segmentation fault via the component Itemfield::fixouterfield...
CVE-2022-32086
CVE-2022-32086 affects MariaDB, with a segmentation fault in Item_field::fix_outer_field observed from MariaDB v10.4 to v10.8. The public reports describe a crash/denial-of-service risk but do not specify an exploit method. Affected versions span 10.4–10.8; the issue is resolved in vendor advisor...