CVE-2022-32082: High severity mariadb vulnerability
Published Jul 1, 2022
·Updated
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
14 affected componentsFixes available
redhat/mariadb<10.9.2
10.9.2
redhat/mariadb<10.8.4
10.8.4
redhat/mariadb<10.7.5
10.7.5
redhat/mariadb<10.6.9
10.6.9
redhat/mariadb<10.5.17
10.5.17
MariaDB MariaDB>=10.5.0<10.5.17
MariaDB MariaDB>=10.6.0<10.6.9
MariaDB MariaDB>=10.7.0<10.7.5
MariaDB MariaDB>=10.8.0<10.8.4
MariaDB MariaDB>=10.9.0<10.9.2
fedoraproject fedora=35
fedoraproject fedora=36
fedoraproject fedora=37
debian/mariadb-10.5
1:10.5.23-0+deb11u11:10.5.28-0+deb11u1
Event History
Jul 1, 2022
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description
Apr 16, 2024
Data Sourced
via Launchpad·02:07 PM
Description
Sep 15, 2024
Data Sourced
via Ubuntu·02:29 PM
RemedyDescriptionSeverityAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2022-32082?
The severity of CVE-2022-32082 is high with a severity value of 7.5.
2
Which software versions are affected by CVE-2022-32082?
MariaDB versions from v10.5 to v10.7 are affected by CVE-2022-32082.
3
How can I fix CVE-2022-32082?
To fix CVE-2022-32082, update MariaDB to version 10.9.2 or later.
4
What is the Common Weakness Enumeration (CWE) ID for CVE-2022-32082?
The CWE ID for CVE-2022-32082 is 617.
5
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].