CVE-2022-27448: High severity MariaDB MariaDB vulnerability
Last updated 24 July 2024
Other sources
There is an Assertion failure in MariaDB Server v10.9 and below via 'node->pcur->relpos == BTRPCURON' at /row/row0mysql.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.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
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.4.25-r0 - Upgrade
Upgrade
alpine/mariadbto a version that resolves this vulnerability.Fixed in 10.5.16-r0 - Upgrade
Upgrade
alpine/mariadbto a version that resolves this vulnerability.Fixed in 10.6.8-r0
Event History
Frequently Asked Questions
What is CVE-2022-27448?
CVE-2022-27448 is a vulnerability in MariaDB Server v10.9 and below that can be exploited via 'node->pcur->rel_pos == BTR_PCUR_ON' at /row/row0mysql.cc.
How severe is CVE-2022-27448?
CVE-2022-27448 has a severity rating of 7.5 (high).
What software versions are affected by CVE-2022-27448?
CVE-2022-27448 affects MariaDB versions 10.3.0 to 10.3.35, 10.4.0 to 10.4.25, 10.5.0 to 10.5.16, 10.6.0 to 10.6.8, and 10.7.0 to 10.7.4.
How can I fix CVE-2022-27448?
To fix CVE-2022-27448, you should upgrade MariaDB to versions 10.3.36, 10.4.26, 10.5.17, 10.6.9, or 10.7.5.
Where can I find more information about CVE-2022-27448?
You can find more information about CVE-2022-27448 at the following references: [1] [2] [3].