CVE-2022-32082: High severity MariaDB MariaDB vulnerability
Last updated 24 July 2024
Other sources
MariaDB v10.5 to v10.7 was discovered to contain an assertion failure at table->getrefcount() == 0 in dict0dict.cc.
— 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.9.2 - Upgrade
Upgrade
redhat/mariadbto a version that resolves this vulnerability.Fixed in 10.8.4 - Upgrade
Upgrade
redhat/mariadbto a version that resolves this vulnerability.Fixed in 10.7.5 - Upgrade
Upgrade
redhat/mariadbto a version that resolves this vulnerability.Fixed in 10.6.9 - Upgrade
Upgrade
redhat/mariadbto a version that resolves this vulnerability.Fixed in 10.5.17 - 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 - Upgrade
Upgrade
alpine/mariadbto a version that resolves this vulnerability.Fixed in 10.5.17-r0 - Upgrade
Upgrade
alpine/mariadbto a version that resolves this vulnerability.Fixed in 10.6.9-r0
Event History
Frequently Asked Questions
What is the severity of CVE-2022-32082?
The severity of CVE-2022-32082 is high with a severity value of 7.5.
Which software versions are affected by CVE-2022-32082?
MariaDB versions from v10.5 to v10.7 are affected by CVE-2022-32082.
How can I fix CVE-2022-32082?
To fix CVE-2022-32082, update MariaDB to version 10.9.2 or later.
What is the Common Weakness Enumeration (CWE) ID for CVE-2022-32082?
The CWE ID for CVE-2022-32082 is 617.
Where can I find more information about CVE-2022-32082?
You can find more information about CVE-2022-32082 in the references provided: [link1], [link2], [link3].