CVE-2025-50080 is a vulnerability identified in Oracle Corporation's MySQL Server, specifically affecting the Stored Procedure component across multiple supported versions: 8.0.0 through 8.0.42, 8.4.0 through 8.4.5, and 9.0.0 through 9.3.0. This vulnerability allows a high-privileged attacker with network access to exploit the server via multiple protocols. The vulnerability does not impact confidentiality or integrity but affects availability by enabling an attacker to cause the MySQL Server to hang or crash repeatedly, resulting in a complete denial of service (DoS). The CVSS 3.1 base score is 4.9, categorized as medium severity, with the vector indicating network attack vector (AV:N), low attack complexity (AC:L), requiring high privileges (PR:H), no user interaction (UI:N), unchanged scope (S:U), no confidentiality or integrity impact (C:N/I:N), and high availability impact (A:H). The underlying weakness corresponds to CWE-400, which relates to uncontrolled resource consumption leading to DoS conditions. No known exploits are currently reported in the wild, and no patches are linked yet. The vulnerability is easily exploitable by an attacker who already has high privileges and network access, emphasizing the importance of controlling privileged access and network exposure. The attack can be executed through multiple protocols, increasing the attack surface. This vulnerability primarily threatens the availability of MySQL Server instances, potentially disrupting database services and dependent applications.

For European organizations, this vulnerability poses a significant risk to the availability of critical database services running MySQL Server versions affected. Organizations relying on MySQL for transactional systems, web applications, or internal data processing could experience service outages or degraded performance due to server hangs or crashes induced by an attacker. This could lead to operational disruptions, loss of productivity, and potential financial losses. While the vulnerability does not compromise data confidentiality or integrity, the denial of service could indirectly impact business continuity and customer trust. Sectors such as finance, healthcare, e-commerce, and public services, which often rely on MySQL databases, may be particularly vulnerable. Given the requirement for high privileges, insider threats or compromised administrative accounts pose a higher risk. Additionally, the ability to exploit via multiple protocols increases the likelihood of attack vectors, especially in complex network environments. The absence of known exploits in the wild currently reduces immediate risk but does not eliminate the threat, especially as attackers may develop exploits post-disclosure.

European organizations should implement the following specific mitigation measures: 1) Immediately audit and restrict high-privileged MySQL user accounts, ensuring the principle of least privilege is enforced and unnecessary administrative accounts are disabled or removed. 2) Harden network access controls by limiting MySQL Server exposure to trusted networks only, using firewalls and network segmentation to restrict protocol access to essential services and known IP addresses. 3) Monitor MySQL server logs and network traffic for unusual activity indicative of exploitation attempts, such as repeated connection attempts or abnormal stored procedure executions. 4) Implement robust authentication and access controls, including multi-factor authentication for administrative access to MySQL servers. 5) Prepare for patch deployment by closely monitoring Oracle's security advisories for the release of a fix and plan timely patch application to affected MySQL versions. 6) Consider deploying database activity monitoring (DAM) solutions to detect and alert on anomalous behaviors related to stored procedures or resource consumption. 7) Develop and test incident response plans to quickly recover from potential DoS attacks, including database failover and backup restoration procedures. These targeted actions go beyond generic advice by focusing on privilege management, network restrictions, and proactive monitoring tailored to the nature of this vulnerability.