CVE-2022-32083: High severity MariaDB MariaDB vulnerability
Last updated 24 July 2024
Other sources
MariaDB v10.2 to v10.6.1 was discovered to contain a segmentation fault via the component Itemsubselect::initexprcachetracker.
— Launchpad
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
redhat/mariadbto a version that resolves this vulnerability.Fixed in 10.8.3 - Upgrade
Upgrade
redhat/mariadbto a version that resolves this vulnerability.Fixed in 10.7.4 - Upgrade
Upgrade
redhat/mariadbto a version that resolves this vulnerability.Fixed in 10.6.8 - Upgrade
Upgrade
redhat/mariadbto a version that resolves this vulnerability.Fixed in 10.5.16 - Upgrade
Upgrade
redhat/mariadbto a version that resolves this vulnerability.Fixed in 10.4.25 - Upgrade
Upgrade
redhat/mariadbto a version that resolves this vulnerability.Fixed in 10.3.35 - Upgrade
Upgrade
redhat/mariadbto a version that resolves this vulnerability.Fixed in 10.2.44 - Upgrade
Upgrade
debian/mariadb-10.5to a version that resolves this vulnerability.Fixed in 1:10.5.23-0+deb11u1Fixed in 1:10.5.28-0+deb11u1
Event History
Frequently Asked Questions
What is CVE-2022-32083?
CVE-2022-32083 is a vulnerability in MariaDB versions 10.2 to 10.6.1 that can cause a segmentation fault.
How does CVE-2022-32083 affect MariaDB?
CVE-2022-32083 affects MariaDB versions 10.2 to 10.6.1, potentially leading to a segmentation fault.
What is the severity of CVE-2022-32083?
CVE-2022-32083 has a severity rating of 7.5 (High).
How can I fix CVE-2022-32083?
To fix CVE-2022-32083, update MariaDB to version 10.8.3 or later.
Where can I find more information about CVE-2022-32083?
You can find more information about CVE-2022-32083 on the MariDB Jira page and the Debian LTS Announce website.