CVE-2024-21239: Medium severity ORACLE MySQL vulnerability
Last updated 12 November 2024
Other sources
Vulnerability in the MySQL Server product of Oracle MySQL (component: InnoDB). Supported versions that are affected are 8.0.39 and prior, 8.4.2 and prior and 9.0.1 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).
— Debian
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/mysql-8.0to a version that resolves this vulnerability.Fixed in 8.0.40-1 - Upgrade
Upgrade
Oracle MySQL (MySQL Server) - InnoDBto a version that resolves this vulnerability.Fixed in 8.0.39 - Upgrade
Upgrade
Oracle MySQL (MySQL Server) - InnoDBto a version that resolves this vulnerability.Fixed in 8.4.2 - Upgrade
Upgrade
Oracle MySQL (MySQL Server) - InnoDBto a version that resolves this vulnerability.Fixed in 9.0.1
Event History
Frequently Asked Questions
What is the severity of CVE-2024-21239?
CVE-2024-21239 is rated as an easily exploitable vulnerability that allows a high privileged attacker with network access to perform unauthorized actions.
How do I fix CVE-2024-21239?
To mitigate CVE-2024-21239, upgrade to MySQL version 8.0.40-1 or later.
Which versions of MySQL are affected by CVE-2024-21239?
CVE-2024-21239 affects MySQL versions 8.0.39 and prior, 8.4.2 and prior, and 9.0.1 and prior.
Is there a workaround for CVE-2024-21239?
Currently, the recommended solution for CVE-2024-21239 is to update to the secure version, as no known workaround exists.
What component of MySQL does CVE-2024-21239 involve?
CVE-2024-21239 involves the InnoDB component of the MySQL Server product.