CVE-2024-21173 in MySQL Server
Summary
by MITRE • 07/17/2024
Vulnerability in the MySQL Server product of Oracle MySQL (component: InnoDB). Supported versions that are affected are 8.0.37 and prior and 8.4.0 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).
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Analysis
by VulDB Data Team • 03/24/2025
The vulnerability identified as CVE-2024-21173 resides within the InnoDB storage engine component of Oracle MySQL server implementations. This flaw affects specific version ranges including all 8.0.x releases up to and including 8.0.37, as well as 8.4.0 and earlier versions of the 8.4.x series. The vulnerability operates at a fundamental level within the database management system's core storage functionality, representing a critical weakness that could severely impact system availability and operational continuity. The affected InnoDB component serves as the primary storage engine for MySQL, handling all data persistence operations and transaction management within the database system.
The technical nature of this vulnerability stems from insufficient input validation and memory management within the InnoDB storage engine's processing routines. An attacker with high privileged access and network connectivity can exploit this weakness through multiple network protocols to trigger a specific sequence of operations that causes the MySQL server to enter a state of indefinite hanging or repeated crashes. The flaw manifests as a denial of service condition where the database server becomes completely unresponsive to legitimate requests, effectively rendering the database service unavailable to authorized users and applications. This vulnerability operates with a CVSS base score of 4.9, classified as a medium severity issue with significant availability impact, indicating that while exploitation requires elevated privileges, the consequences can be devastating to system operations.
The operational impact of this vulnerability extends beyond simple service disruption, potentially affecting business continuity and data availability for organizations relying on MySQL databases. When successfully exploited, the vulnerability can cause complete system downtime that may require manual intervention to restore normal operations, including database server restarts and potential data recovery procedures. Organizations utilizing affected MySQL versions face substantial risk of service interruptions that could impact critical business applications, reporting systems, and automated processes dependent on database availability. The high privilege requirement for exploitation suggests that this vulnerability is more likely to be targeted by insiders or attackers who have already gained elevated access to the system, making it particularly dangerous in environments where administrative credentials are compromised.
Mitigation strategies for CVE-2024-21173 should prioritize immediate patching of affected MySQL installations to the latest available versions that contain the necessary security fixes. Organizations should implement comprehensive monitoring of database server performance and availability to detect potential exploitation attempts or system instability patterns. Network segmentation and access controls should be reinforced to limit exposure of database servers to only necessary network segments and authorized users. The vulnerability aligns with CWE-129 which addresses improper validation of array indices, and may relate to ATT&CK technique T1499.004 for endpoint denial of service through resource exhaustion. Security teams should also consider implementing database activity monitoring solutions to detect anomalous patterns that might indicate exploitation attempts, and maintain robust backup and recovery procedures to minimize impact should the vulnerability be successfully exploited in a production environment.