Skip to main content

CVE-2025-50103: Difficult to exploit 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-50103cvecve-2025-50103
Published: Tue Jul 15 2025 (07/15/2025, 19:27:50 UTC)
Source: CVE Database V5
Vendor/Project: Oracle Corporation
Product: MySQL Server

Description

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Security: LDAP Auth). Supported versions that are affected are 9.0.0-9.3.0. Difficult to exploit 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.4 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H).

AI-Powered Analysis

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

Technical Analysis

CVE-2025-50103 is a vulnerability identified in Oracle Corporation's MySQL Server, specifically affecting versions 9.0.0 through 9.3.0. The vulnerability resides in the LDAP Authentication component of the MySQL Server. It is characterized as a denial-of-service (DoS) vulnerability that allows a high-privileged attacker with network access to cause the MySQL Server to hang or crash repeatedly, resulting in a complete denial of service. The attack vector requires network access and high privileges, and it does not require user interaction. The vulnerability is difficult to exploit, as indicated by the high attack complexity (AC:H) in the CVSS vector. The CVSS 3.1 base score is 4.4, reflecting a medium severity primarily due to its impact on availability (A:H), with no impact on confidentiality or integrity. The CWE classification is CWE-400, which relates to uncontrolled resource consumption leading to DoS conditions. No known exploits are currently reported in the wild, and no patches or fixes have been linked yet. The vulnerability could be triggered via multiple network protocols supported by MySQL Server, leveraging the LDAP authentication mechanism to induce resource exhaustion or crash conditions. Given the requirement for high privileges, the attacker would likely need to have already compromised an account with elevated rights or have internal network access to exploit this vulnerability effectively.

Potential Impact

For European organizations, this vulnerability poses a risk primarily to the availability of critical database services running MySQL Server versions 9.0.0 to 9.3.0. Organizations relying on MySQL for business-critical applications could experience service interruptions, leading to operational downtime, potential loss of productivity, and disruption of dependent services. Although the vulnerability does not compromise data confidentiality or integrity, the denial-of-service impact could affect sectors where continuous database availability is essential, such as financial services, healthcare, e-commerce, and public administration. The requirement for high privileges and network access somewhat limits the attack surface to internal threats or attackers who have already gained elevated access, but insider threats or lateral movement by attackers within a network could exploit this vulnerability to disrupt services. The absence of known exploits in the wild reduces immediate risk, but the medium severity rating and potential impact on availability warrant proactive mitigation to prevent exploitation, especially in environments with sensitive or critical operations.

Mitigation Recommendations

European organizations should implement the following specific mitigation strategies: 1) Upgrade MySQL Server to a patched version as soon as Oracle releases a fix for CVE-2025-50103. Until a patch is available, consider temporarily disabling LDAP authentication if feasible, or restrict its use to trusted internal networks only. 2) Enforce strict network segmentation and access controls to limit network exposure of MySQL servers, ensuring that only authorized and trusted hosts can communicate with the database server over the relevant protocols. 3) Implement robust privilege management to minimize the number of accounts with high privileges on MySQL servers, reducing the likelihood of an attacker having the necessary access to exploit this vulnerability. 4) Monitor MySQL server logs and network traffic for unusual patterns indicative of attempts to exploit LDAP authentication or cause resource exhaustion. 5) Employ rate limiting or connection throttling on MySQL server interfaces to mitigate the impact of potential DoS attempts. 6) Conduct regular security audits and penetration testing focused on internal threat vectors, especially for high-privilege accounts and authentication mechanisms. 7) Prepare incident response plans specifically addressing denial-of-service scenarios affecting database availability to ensure rapid recovery and continuity of operations.

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: 6876b00ca83201eaacd044bf

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

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

Last updated: 8/21/2025, 7:27:15 AM

Views: 26

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