Skip to main content

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

Medium
VulnerabilityCVE-2024-20963cvecve-2024-20963
Published: Tue Jan 16 2024 (01/16/2024, 21:41:22 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: Encryption). Supported versions that are affected are 8.0.35 and prior and 8.2.0 and prior. 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).

AI-Powered Analysis

AILast updated: 07/03/2025, 16:42:01 UTC

Technical Analysis

CVE-2024-20963 is a vulnerability identified in Oracle Corporation's MySQL Server, specifically affecting versions 8.0.35 and prior, as well as 8.2.0 and prior. The vulnerability resides in the server's security encryption component. It allows a low-privileged attacker with network access—via multiple protocols—to exploit the flaw without requiring user interaction. The attacker must have some level of privileges (PR:L), but no elevated privileges are necessary. Exploitation can lead to a denial-of-service (DoS) condition by causing the MySQL Server to hang or crash repeatedly, effectively rendering the database service unavailable. The CVSS 3.1 base score of 6.5 reflects a medium severity primarily due to the impact on availability (A:H), with no direct impact on confidentiality or integrity. The vulnerability is easily exploitable over the network, which increases the risk profile, especially in environments where MySQL servers are exposed or accessible via multiple protocols. No known exploits are currently reported in the wild, but the ease of exploitation and the critical role of MySQL in many infrastructures make this a significant concern. The vulnerability does not require user interaction and affects a widely used database platform, making it a potential vector for disruption in enterprise environments.

Potential Impact

For European organizations, the impact of CVE-2024-20963 can be substantial, particularly for those relying heavily on MySQL Server for critical applications, data storage, and web services. A successful attack can cause service outages, leading to operational disruptions, loss of business continuity, and potential financial losses. The denial-of-service nature of the vulnerability means that while data confidentiality and integrity remain intact, the availability of services is compromised, which can affect customer-facing applications, internal business processes, and compliance with service-level agreements (SLAs). Organizations in sectors such as finance, healthcare, e-commerce, and public services—where MySQL is commonly deployed—may face increased risks. Additionally, the requirement for only low privileges and network access broadens the attack surface, especially in environments with insufficient network segmentation or exposed database ports. The medium severity rating suggests that while the vulnerability is not critical, it should be addressed promptly to avoid potential exploitation and service disruption.

Mitigation Recommendations

To mitigate CVE-2024-20963 effectively, European organizations should: 1) Apply the latest patches and updates from Oracle as soon as they become available, as patching is the most definitive mitigation. 2) Restrict network access to MySQL servers by implementing strict firewall rules and network segmentation to limit exposure to trusted hosts and services only. 3) Enforce the principle of least privilege for database users and services to minimize the risk posed by low-privileged accounts. 4) Monitor MySQL server logs and network traffic for unusual activity or repeated connection attempts that could indicate exploitation attempts. 5) Consider deploying intrusion detection/prevention systems (IDS/IPS) tuned to detect anomalies related to MySQL traffic. 6) Disable or limit unused protocols and services that provide network access to MySQL to reduce the attack surface. 7) Regularly review and audit MySQL server configurations and access controls to ensure compliance with security best practices. These targeted actions go beyond generic advice by focusing on reducing exposure, limiting privileges, and enhancing detection capabilities specific to this vulnerability.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
oracle
Date Reserved
2023-12-07T22:28:10.628Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 683dbfa6182aa0cae249832d

Added to database: 6/2/2025, 3:13:42 PM

Last enriched: 7/3/2025, 4:42:01 PM

Last updated: 8/11/2025, 10:04:47 PM

Views: 10

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