Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-20974: 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

0
Medium
VulnerabilityCVE-2024-20974cvecve-2024-20974
Published: Sat Feb 17 2024 (02/17/2024, 01:50:20 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.35 and prior and 8.2.0 and prior. 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: 11/04/2025, 21:57:47 UTC

Technical Analysis

CVE-2024-20974 is a vulnerability identified in the Oracle MySQL Server product, specifically within the Server Optimizer component. It affects all versions up to 8.0.35 and 8.2.0 and prior. The flaw allows an attacker who already possesses high-level privileges and network access through multiple protocols to exploit the vulnerability to cause the MySQL Server to hang or crash repeatedly, resulting in a complete denial-of-service (DoS) condition. The CVSS 3.1 base score is 4.9, indicating a medium severity primarily due to its impact on availability. The attack vector is network-based (AV:N), with low attack complexity (AC:L), but requires high privileges (PR:H) and no user interaction (UI:N). The scope remains unchanged (S:U), and there is no impact on confidentiality or integrity (C:N/I:N), only availability (A:H). This vulnerability does not allow data theft or modification but can disrupt critical database services, potentially halting dependent applications. No public exploits or active exploitation in the wild have been reported yet. The vulnerability underscores the importance of controlling privileged access and securing network exposure of MySQL servers. Since MySQL is widely used in enterprise environments, especially for web applications and data storage, this DoS vulnerability could have significant operational impacts if exploited.

Potential Impact

For European organizations, the primary impact of CVE-2024-20974 is the potential for denial-of-service attacks against MySQL Server instances, which could disrupt business-critical applications relying on these databases. This could lead to downtime, loss of productivity, and potential financial losses, especially in sectors such as finance, telecommunications, government, and e-commerce where MySQL is prevalent. The requirement for high privileges limits the attack surface to insiders or attackers who have already compromised administrative credentials, but the network-based nature means that once such access is obtained, the attacker can cause repeated server crashes. This could also affect cloud service providers and managed service providers hosting MySQL databases for European clients, amplifying the impact. Additionally, disruption of MySQL services could affect data availability for compliance with regulations like GDPR, potentially leading to regulatory scrutiny if service interruptions impact data subject rights or business continuity.

Mitigation Recommendations

To mitigate CVE-2024-20974, European organizations should: 1) Apply Oracle's security patches promptly once released for the affected MySQL versions. 2) Restrict network access to MySQL servers using firewalls and network segmentation to limit exposure to trusted hosts and administrative users only. 3) Enforce strict access controls and monitor privileged accounts to prevent unauthorized privilege escalation. 4) Implement robust logging and anomaly detection to identify unusual MySQL server behavior indicative of attempted exploitation or crashes. 5) Consider deploying MySQL high-availability configurations and failover mechanisms to minimize downtime in case of DoS incidents. 6) Regularly audit and update MySQL configurations to disable unnecessary protocols or services that could be exploited. 7) Educate administrators on the risks of high-privilege access and enforce multi-factor authentication for administrative access to reduce insider threat risks. 8) Maintain up-to-date backups to enable rapid recovery if service disruption occurs.

Need more detailed analysis?Get Pro

Technical Details

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

Threat ID: 690a474a6d939959c8022378

Added to database: 11/4/2025, 6:34:50 PM

Last enriched: 11/4/2025, 9:57:47 PM

Last updated: 11/5/2025, 2:06:20 PM

Views: 2

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

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