Cloudanix VulnDB

CVE-2024-21194

Medium · 4.9

CVSS

4.9

EPSS

0.9%

Published

Oct 15, 2024

CISA due date

—

Cloudanix analysis

Schedule a fix SSVC: Track

A flaw in the database software lets someone who already has strong access rights over the network shut the whole database down, stopping applications that rely on it from working.

Exploitation
Remote Authenticated
Attacker needs
High Privilege
Complexity
Low
Impact
Denial Of Service
Component
Application
Class
Denial of service
Remediation
Upgrade
Effort
Medium
Patch risk
Low

What it actually does

High-privileged network attacker can trigger a hang or repeatable crash in the InnoDB component, resulting in complete denial of service for the MySQL Server process.

Why it matters to the business

Database services can be taken offline on demand, interrupting applications and business operations that depend on MySQL availability; the low EPSS and lack of KEV status indicate limited real-world urgency but still require prompt patching of affected 8.0/8.4/9.0 releases.

How an attack unfolds

An attacker who already possesses high-privileged network credentials connects to the MySQL instance over any supported protocol and sends a sequence of specially crafted requests that exercise the vulnerable code path inside InnoDB, causing the server process to hang or crash.

How to fix it

Upgrade MySQL Server to a version newer than 8.0.39, 8.4.2, or 9.0.1 as appropriate for the release line; apply the vendor-supplied patches that address the InnoDB denial-of-service condition.

How to confirm the fix worked

Confirm the installed MySQL version is newer than the affected releases listed in the advisory; run the vendor's diagnostic or regression test suite against InnoDB under load to verify the crash/hang condition no longer occurs.

Typical attack path

  1. Obtain high-privileged network credentials for the MySQL instance
  2. Establish a connection using any supported protocol
  3. Submit crafted requests that reach the vulnerable InnoDB code path
  4. Trigger repeated crashes or a persistent hang to achieve denial of service

How to detect it

Inspect database server logs and monitoring systems for repeated unexpected shutdowns or crash signatures around the time of high-privileged connections; correlate with authentication events from privileged accounts.

What your security team should do

  • Prioritize patching all MySQL 8.0, 8.4, and 9.0 instances within the next maintenance window
  • Review database access controls to ensure only necessary high-privileged accounts exist
  • Monitor for unexpected server restarts or availability alerts as an interim detection measure

The record

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).

Affected packages

Ecosystem Package Introduced Fixed
AlmaLinux:8 mecab 0 0.996-2.module_el8.10.0+3965+b415b607
AlmaLinux:8 mecab 0 0.996-2.module_el8.6.0+3340+d764b636
AlmaLinux:8 mecab-devel 0 0.996-2.module_el8.10.0+3965+b415b607
AlmaLinux:8 mecab-devel 0 0.996-2.module_el8.6.0+3340+d764b636
AlmaLinux:8 mecab-ipadic 0 2.7.0.20070801-17.module_el8.10.0+3965+b415b607
AlmaLinux:8 mecab-ipadic-EUCJP 0 2.7.0.20070801-17.module_el8.10.0+3965+b415b607
AlmaLinux:8 mysql 0 8.0.41-1.module_el8.10.0+3965+b415b607
AlmaLinux:8 mysql-common 0 8.0.41-1.module_el8.10.0+3965+b415b607
AlmaLinux:8 mysql-devel 0 8.0.41-1.module_el8.10.0+3965+b415b607
AlmaLinux:8 mysql-errmsg 0 8.0.41-1.module_el8.10.0+3965+b415b607
AlmaLinux:8 mysql-libs 0 8.0.41-1.module_el8.10.0+3965+b415b607
AlmaLinux:8 mysql-server 0 8.0.41-1.module_el8.10.0+3965+b415b607
AlmaLinux:8 mysql-test 0 8.0.41-1.module_el8.10.0+3965+b415b607
AlmaLinux:9 mysql 0 8.0.41-2.el9_5
AlmaLinux:9 mysql-common 0 8.0.41-2.el9_5
AlmaLinux:9 mysql-devel 0 8.0.41-2.el9_5
AlmaLinux:9 mysql-errmsg 0 8.0.41-2.el9_5
AlmaLinux:9 mysql-libs 0 8.0.41-2.el9_5
AlmaLinux:9 mysql-server 0 8.0.41-2.el9_5
AlmaLinux:9 mysql-test 0 8.0.41-2.el9_5
Rocky Linux:8 mecab 0 0:0.996-2.module+el8.10.0+1676+9b4b6e24
Rocky Linux:8 mecab-ipadic 0 0:2.7.0.20070801-17.module+el8.10.0+1937+28fbbc83
Rocky Linux:8 mysql 0 0:8.0.41-1.module+el8.10.0+1937+28fbbc83.0.1
Rocky Linux:9 mysql 0 0:8.0.41-2.el9_5
Ubuntu:14.04:LTS mysql-5.5 0 No fix
Ubuntu:16.04:LTS mariadb-10.0 0 No fix
Ubuntu:16.04:LTS percona-server-5.6 0 No fix
Ubuntu:16.04:LTS percona-xtradb-cluster-5.6 0 No fix
Ubuntu:18.04:LTS mariadb-10.1 0 No fix
Ubuntu:20.04:LTS mariadb-10.3 0 No fix
Ubuntu:20.04:LTS mysql-8.0 0 No fix
Ubuntu:20.04:LTS mysql-8.0 0 8.0.40-0ubuntu0.20.04.1
Ubuntu:22.04:LTS mariadb-10.6 0 No fix
Ubuntu:22.04:LTS mysql-8.0 0 No fix
Ubuntu:22.04:LTS mysql-8.0 0 8.0.40-0ubuntu0.22.04.1
Ubuntu:24.04:LTS mariadb 0 No fix
Ubuntu:24.04:LTS mysql-8.0 0 No fix
Ubuntu:24.04:LTS mysql-8.0 0 8.0.40-0ubuntu0.24.04.1
Ubuntu:24.10 mariadb 0 No fix
Ubuntu:24.10 mysql-8.0 0 No fix
Ubuntu:24.10 mysql-8.0 0 8.0.40-0ubuntu0.24.10.1
Ubuntu:25.04 mariadb 0 No fix
Ubuntu:25.10 mariadb 0 No fix
Ubuntu:Pro:14.04:LTS mysql-5.5 0 No fix
Ubuntu:Pro:16.04:LTS mariadb-10.0 0 No fix
Ubuntu:Pro:16.04:LTS mysql-5.7 0 No fix
Ubuntu:Pro:16.04:LTS percona-server-5.6 0 No fix
Ubuntu:Pro:16.04:LTS percona-xtradb-cluster-5.6 0 No fix
Ubuntu:Pro:18.04:LTS mariadb-10.1 0 No fix
Ubuntu:Pro:18.04:LTS mysql-5.7 0 No fix
Ubuntu:Pro:20.04:LTS mariadb-10.3 0 No fix

Related vulnerabilities