Skip to main content

CVE-2025-50101: 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. in Oracle Corporation MySQL Server

Medium
VulnerabilityCVE-2025-50101cvecve-2025-50101
Published: Tue Jul 15 2025 (07/15/2025, 19:27:49 UTC)
Source: CVE Database V5
Vendor/Project: Oracle Corporation
Product: MySQL Server

Description

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). 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 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).

AI-Powered Analysis

AILast updated: 07/22/2025, 20:38:18 UTC

Technical Analysis

CVE-2025-50101 is a medium-severity vulnerability affecting Oracle Corporation's MySQL Server, specifically within the Server Optimizer component. It impacts 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. The vulnerability allows a high-privileged attacker with network access via multiple protocols to cause a denial-of-service (DoS) condition by triggering a hang or repeated crash of the MySQL Server process. The CVSS 3.1 base score is 4.9, reflecting an availability impact without compromising confidentiality or integrity. The attack vector is network-based (AV:N), requires low attack complexity (AC:L), but demands high privileges (PR:H) and no user interaction (UI:N). The vulnerability is categorized under CWE-400, indicating a resource exhaustion or DoS condition. No known exploits are currently reported in the wild, and no patches have been linked yet. The vulnerability does not allow unauthorized data access or modification but can disrupt database availability, potentially impacting dependent applications and services. The lack of authentication bypass means that attackers must already have high privileges on the MySQL server, which limits the scope but still poses a significant risk in environments where privileged access is attainable remotely or through compromised credentials.

Potential Impact

For European organizations, this vulnerability poses a risk primarily to the availability of MySQL database services. Many enterprises, including financial institutions, healthcare providers, and public sector organizations across Europe, rely heavily on MySQL for critical data storage and application backends. A successful DoS attack could disrupt business operations, cause downtime, and lead to service unavailability, impacting customer trust and regulatory compliance, especially under GDPR where service continuity is important. Organizations with remote administrative access to MySQL servers are particularly vulnerable. The impact is heightened in sectors where database uptime is critical, such as banking, telecommunications, and e-government services. Although the vulnerability does not expose data confidentiality or integrity, the availability disruption can cascade into operational and reputational damage. Given the requirement for high privileges, the threat is more severe in environments with weak internal access controls or where privileged credentials are exposed or reused.

Mitigation Recommendations

European organizations should implement the following specific mitigations: 1) Restrict network access to MySQL servers strictly to trusted administrative hosts and use network segmentation to limit exposure. 2) Enforce strong authentication and authorization policies to reduce the risk of privilege escalation or credential compromise. 3) Monitor and audit privileged user activities on MySQL servers to detect suspicious behavior early. 4) Apply principle of least privilege for MySQL accounts, ensuring that only necessary users have high-level privileges. 5) Deploy rate limiting or connection throttling at the network or application layer to mitigate potential DoS attempts. 6) Stay alert for Oracle's official patches or updates addressing this vulnerability and apply them promptly once available. 7) Consider implementing failover and redundancy mechanisms for MySQL services to minimize downtime impact. 8) Use intrusion detection/prevention systems (IDS/IPS) tuned to detect anomalous MySQL traffic patterns that could indicate exploitation attempts.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
oracle
Date Reserved
2025-06-11T22:56:56.113Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6876b00ca83201eaacd044b9

Added to database: 7/15/2025, 7:46:20 PM

Last enriched: 7/22/2025, 8:38:18 PM

Last updated: 8/5/2025, 8:26:48 AM

Views: 8

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats