CVE-2022-21417: Medium severity mysql vulnerability
Last updated 24 July 2024
Other sources
Vulnerability in the MySQL Server product of Oracle MySQL (component: InnoDB). Supported versions that are affected are 5.7.37 and prior and 8.0.28 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server.
External References:
https://www.oracle.com/security-alerts/cpuapr2022.html#AppendixMSQL
— Red Hat
Vulnerability in the MySQL Server product of Oracle MySQL (component: InnoDB). Supported versions that are affected are 5.7.37 and prior and 8.0.28 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
— Launchpad
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2022-21417?
CVE-2022-21417 is considered an easily exploitable vulnerability that allows high privileged attackers with network access to compromise affected MySQL server instances.
How do I fix CVE-2022-21417?
To fix CVE-2022-21417, upgrade your MySQL server to version 5.7.38 or later, or to version 8.0.29 or later.
Which MySQL server versions are affected by CVE-2022-21417?
MySQL server versions 5.7.37 and prior, and 8.0.28 and prior are affected by CVE-2022-21417.
What components are impacted by CVE-2022-21417?
CVE-2022-21417 impacts the InnoDB component of the Oracle MySQL server.
Can I check my MySQL version for CVE-2022-21417?
Yes, you can check your MySQL version by running the command 'SELECT VERSION();' in your MySQL client.