CVE-2022-27448: High severity mariadb vulnerability
Published Apr 14, 2022
·Updated
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
12 affected componentsFixes available
redhat/mariadb<10.7.4
10.7.4
redhat/mariadb<10.6.8
10.6.8
redhat/mariadb<10.5.16
10.5.16
redhat/mariadb<10.4.25
10.4.25
redhat/mariadb<10.3.35
10.3.35
MariaDB MariaDB>=10.3.0<10.3.35
MariaDB MariaDB>=10.4.0<10.4.25
MariaDB MariaDB>=10.5.0<10.5.16
MariaDB MariaDB>=10.6.0<10.6.8
MariaDB MariaDB>=10.7.0<10.7.4
Debian Debian Linux=10.0
debian/mariadb-10.5
1:10.5.23-0+deb11u11:10.5.28-0+deb11u1
Remediation
Patch Available
Event History
Apr 14, 2022
CVE Published
via MITRE·12:56 PM
Data Sourced
via MITRE·12:56 PM
Description
Apr 16, 2024
Data Sourced
via Launchpad·02:06 PM
Description
Sep 15, 2024
Data Sourced
via Ubuntu·02:29 PM
RemedyDescriptionSeverityAffected Software
Frequently Asked Questions
1
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.
2
How severe is CVE-2022-27448?
CVE-2022-27448 has a severity rating of 7.5 (high).
3
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.
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.
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].