CVE-2025-50078 in MySQL Server
Summary
by MITRE • 07/15/2025
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: DML). Supported versions that are affected are 8.0.0-8.0.42, 8.4.0-8.4.5 and 9.0.0-9.3.0. Easily exploitable vulnerability allows low 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 6.5 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 12/02/2025
This vulnerability resides within the MySQL Server's Data Manipulation Language component and represents a significant availability risk for affected database systems. The flaw affects specific version ranges including 8.0.0 through 8.0.42, 8.4.0 through 8.4.5, and 9.0.0 through 9.3.0, indicating it spans multiple major releases and reflects a persistent issue in the database engine's handling of certain DML operations. The vulnerability's classification as easily exploitable means that attackers with minimal privileges and network access can leverage this weakness, making it particularly dangerous in environments where database access is broadly distributed. The attack vector through multiple protocols suggests the flaw exists at a foundational level rather than being protocol-specific, potentially affecting connections via TCP/IP, Unix sockets, or other supported communication channels.
The technical nature of this vulnerability manifests as a complete denial of service condition that can either cause the MySQL server to hang indefinitely or trigger frequently repeatable crashes, effectively rendering the database service unavailable to legitimate users. This behavior aligns with CWE-400 vulnerability type, which encompasses issues that can lead to resource exhaustion or system instability through improper handling of input data. The CVSS 3.1 score of 6.5 reflects the high impact on availability, with the attack complexity rated as low and requiring only local privileges or network access. The vulnerability's potential for causing repeated crashes suggests that the underlying flaw involves improper memory management or state handling during DML processing, where malformed input or specific query patterns can trigger an infinite loop or memory corruption that ultimately leads to service termination.
The operational impact of this vulnerability extends beyond simple service disruption to potentially compromise entire database infrastructures, especially in mission-critical applications where MySQL serves as a core data repository. Organizations running affected versions face the risk of extended downtime, data access interruptions, and potential cascading failures in applications that depend on database availability. The low privilege requirement means that even users with minimal database permissions could exploit this vulnerability, making it particularly concerning for environments with extensive user access or where privilege escalation is possible through other means. This vulnerability directly relates to the ATT&CK technique T1499.004 which involves network denial of service attacks targeting database services, and represents a critical gap in the security posture of MySQL installations that could be leveraged by both malicious actors and automated exploit frameworks.
Organizations should immediately implement mitigations including applying the latest security patches from Oracle, which will address the specific DML handling issue causing the instability. Network segmentation and access controls should be enforced to limit the attack surface, particularly restricting network access to database servers from trusted sources only. Monitoring systems should be enhanced to detect unusual patterns that might indicate exploitation attempts, including repeated connection failures or service restarts. Additionally, implementing database firewalls or connection pooling solutions can provide additional layers of protection by filtering potentially malicious queries before they reach the vulnerable server components. The vulnerability's scope across multiple version ranges indicates that organizations should conduct comprehensive inventory audits to identify all affected systems and prioritize patching based on risk assessment and business impact considerations.