CVE-2024-21051 in MySQL Server
Summary
by MITRE • 04/17/2024
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: DML). Supported versions that are affected are 8.0.34 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 • 09/06/2025
This vulnerability resides within the MySQL Server's Data Manipulation Language component, specifically affecting versions 8.0.34 and earlier. The flaw represents a critical availability threat that can be exploited by attackers with high privileges and network access through multiple protocols. The vulnerability's classification as easily exploitable indicates that the attack vector requires minimal complexity and can be executed with relatively straightforward techniques. The affected component operates within the server's core functionality, making it a prime target for adversaries seeking to disrupt database services. This particular vulnerability demonstrates how even seemingly routine database operations can become weaponized when underlying code contains implementation flaws that allow for denial of service conditions.
The technical nature of this vulnerability manifests as a condition that can cause complete denial of service through either hanging or repeated crashes of the MySQL Server process. The attack requires an authenticated user with high privileges, suggesting that the flaw may be triggered through legitimate administrative functions or commands that are improperly validated or handled. The CVSS score of 4.9 reflects the availability impact severity, indicating that while the vulnerability does not directly compromise data integrity or confidentiality, it can render the database service completely unusable. The vector analysis shows network accessibility with low attack complexity and high privileges required, suggesting that the vulnerability may be exploitable from external networks but requires an existing authenticated session or administrative access level. This characteristic places the vulnerability in the category of internal threats or compromised accounts that could be leveraged by attackers to cause service disruption.
The operational impact of this vulnerability extends beyond simple service interruption, as it can create cascading effects throughout systems that depend on MySQL database availability. Organizations utilizing affected MySQL versions may experience significant downtime, particularly in environments where database connectivity is critical for business operations. The repeated crash potential indicates that once exploited, the vulnerability can cause sustained disruption rather than a one-time service interruption, potentially requiring manual intervention to restore service. The high privilege requirement suggests that the vulnerability may be more relevant in environments where administrative access is more prevalent or where privilege escalation techniques have already been successful. This makes the vulnerability particularly concerning in enterprise environments where database administrators maintain elevated access levels and where a single compromised account could lead to widespread service disruption.
Mitigation strategies for this vulnerability should focus on immediate version upgrades to MySQL 8.0.35 or later, which contain the necessary patches to address the flaw. Organizations should also implement network segmentation to limit access to MySQL services and enforce strict authentication controls to prevent unauthorized access. The principle of least privilege should be enforced for database administrative accounts, ensuring that only necessary personnel have high-privilege access. Network monitoring should be enhanced to detect unusual patterns that might indicate exploitation attempts, particularly around administrative commands or DML operations. Additionally, implementing intrusion detection systems and regular vulnerability assessments can help identify potential exploitation attempts before they cause service disruption. Organizations should also maintain detailed incident response procedures specifically addressing database service disruptions and ensure that backup and recovery processes are tested regularly to minimize impact during exploitation events. The vulnerability's classification under CWE categories related to resource management and input validation highlights the importance of proper code review and testing procedures for database server components.