CVE-2024-21050 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
The vulnerability identified as CVE-2024-21050 represents a critical availability threat within Oracle MySQL Server version 8.0.34 and earlier releases. This flaw resides within the Server: DML component, which processes data manipulation language operations including select, insert, update, and delete commands. The vulnerability's classification as easily exploitable indicates that attackers with high privileges and network access can readily leverage this weakness to compromise the target system. The attack vector operates through multiple protocols, suggesting that the vulnerability can be exploited across various network communication channels that MySQL supports. The CVSS score of 4.9 reflects the significant impact on system availability, with the attack requiring only high privileges and no user interaction, making it particularly dangerous in environments where privileged accounts exist.
The technical nature of this vulnerability manifests as a condition that can cause complete denial of service through either system hanging or repeated crashes of the MySQL Server process. This type of flaw typically originates from improper handling of specific data operations or memory management issues within the DML processing engine. The vulnerability's impact extends beyond simple service disruption as it can lead to complete system unavailability, requiring manual intervention to restore normal operations. Attackers exploiting this weakness can repeatedly trigger the crash condition, creating sustained denial of service scenarios that can persist until the system is manually restarted or the underlying issue is patched. This characteristic makes the vulnerability particularly concerning for production environments where database availability is critical for business operations.
The operational impact of CVE-2024-21050 significantly affects database server reliability and business continuity. Organizations running affected MySQL versions face the risk of unauthorized disruption of database services, potentially leading to extended downtime for applications dependent on these databases. The vulnerability's requirement for high-privileged access suggests that it may be exploited by insider threats or attackers who have already gained elevated system credentials. This attack scenario is particularly dangerous because it can be executed without requiring extensive technical expertise or user interaction, making it accessible to threat actors with moderate skill levels. The complete denial of service condition can result in cascading failures across dependent applications and services that rely on the database for their operations.
Security mitigations for CVE-2024-21050 primarily focus on immediate patching and system hardening measures. Organizations should prioritize upgrading to MySQL Server version 8.0.35 or later, which contains the necessary fixes for this vulnerability. Network segmentation and access control measures should be implemented to limit the attack surface, particularly restricting network access to privileged accounts. Monitoring systems should be enhanced to detect unusual patterns of database crashes or hanging conditions that might indicate exploitation attempts. The vulnerability aligns with CWE-119, which addresses memory safety issues, and maps to ATT&CK technique T1499.004 for network denial of service attacks. Additionally, implementing database activity monitoring and anomaly detection systems can help identify potential exploitation attempts before they cause significant disruption to services. Regular security assessments and vulnerability scanning should be conducted to identify and remediate similar issues in database environments.