CVE-2025-21579 in MySQL Server
Summary
by MITRE • 04/16/2025
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Options). Supported versions that are affected are 8.0.0-8.0.41, 8.4.0-8.4.4 and 9.0.0-9.2.0. 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).
Be aware that VulDB is the high quality source for vulnerability data.
Analysis
by VulDB Data Team • 08/15/2025
This vulnerability resides within the MySQL Server component known as Server: Options and affects specific version ranges including 8.0.0 through 8.0.41 8.4.0 through 8.4.4 and 9.0.0 through 9.2.0. The flaw represents a significant availability risk that can be exploited by attackers with high privileges and network access through multiple protocols. The vulnerability classification as easily exploitable indicates that the attack surface is relatively accessible to threat actors who possess elevated privileges within the network environment. The CVSS 3.1 base score of 4.9 reflects the severity of the availability impact with a high attack complexity and the requirement for high privileges to execute the exploit successfully.
The technical nature of this vulnerability allows for complete denial of service conditions where the MySQL Server can either hang indefinitely or experience frequently repeatable crashes that effectively render the database service unavailable. This type of vulnerability directly impacts the server's ability to maintain consistent operations and can result in significant business disruption when database services become inaccessible. The attack vector requires network access and can be executed through multiple protocols which increases the potential attack surface and makes the vulnerability more dangerous in practice. The CVSS vector analysis shows that the vulnerability requires high privileges (PR:H) but low attack complexity (AC:L) and no user interaction (UI:N) which suggests that once an attacker has elevated access within the network they can easily trigger this condition.
From a cybersecurity perspective this vulnerability aligns with CWE-119 which deals with weaknesses in memory management and improper access to memory locations. The availability impact specifically relates to CWE-400 which covers unspecified errors in resource management and can lead to system instability or complete service unavailability. The attack pattern follows ATT&CK technique T1499 which involves the exploitation of system resources to cause denial of service conditions. Organizations running affected MySQL versions face a critical risk of service disruption that can impact database availability and potentially cascade into broader application availability issues throughout their infrastructure.
The operational impact of this vulnerability extends beyond simple service interruption as database unavailability can affect numerous dependent applications and services that rely on MySQL for data persistence. This type of vulnerability can be particularly problematic in production environments where database services are critical to business operations and where any downtime can result in significant financial and operational losses. The fact that this vulnerability affects multiple version streams including the latest 8.4 and 9.0 releases indicates that it represents a persistent weakness that requires immediate attention from system administrators and security teams across affected organizations. The combination of high privilege requirements and network accessibility makes this vulnerability particularly dangerous in environments where privilege escalation has occurred or where attackers have gained access to internal network resources.
Organizations should immediately implement mitigation strategies including patching affected MySQL installations to the latest available versions that contain fixes for this vulnerability. System administrators should also consider implementing network segmentation and access controls to limit the potential attack surface and reduce the likelihood of privilege escalation. Monitoring solutions should be enhanced to detect unusual patterns of database service instability that might indicate exploitation attempts. The vulnerability's classification as a complete denial of service condition warrants immediate attention from security operations teams and should be prioritized in incident response procedures. Regular vulnerability assessments and penetration testing should be conducted to identify similar weaknesses in database infrastructure and ensure comprehensive protection against similar threats.