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-20978: 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-20978cvecve-2024-20978
Published: Sat Feb 17 2024 (02/17/2024, 01:50:21 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:20 UTC

Technical Analysis

CVE-2024-20978 is a vulnerability in the Oracle MySQL Server, specifically within the Server Optimizer component, affecting versions 8.0.35 and earlier, as well as 8.2.0 and earlier. The flaw allows a high privileged attacker who has network access via multiple protocols to cause the MySQL Server to hang or crash repeatedly, resulting in a complete denial-of-service (DoS) condition. The vulnerability does not compromise data confidentiality or integrity but severely impacts availability. The attack vector is network-based (AV:N), with low attack complexity (AC:L), requiring high privileges (PR:H), and no user interaction (UI:N). The scope is unchanged (S:U), meaning the impact is limited to the vulnerable component. The CVSS 3.1 base score is 4.9, reflecting a medium severity primarily due to availability impact. Although no known exploits are currently reported in the wild, the vulnerability is considered easily exploitable by attackers with the necessary privileges. The underlying weakness is classified under CWE-400, which relates to uncontrolled resource consumption leading to denial-of-service. This vulnerability poses a risk to organizations that rely on MySQL Server for critical database operations, as successful exploitation can disrupt services and impact business continuity. Oracle has not yet published patches at the time of this report, so organizations must monitor for updates and apply them promptly once available. Network segmentation and strict access controls are essential to limit exposure. Monitoring for unusual MySQL server behavior can help detect exploitation attempts early.

Potential Impact

For European organizations, the primary impact of CVE-2024-20978 is the potential for denial-of-service attacks against MySQL Server instances, which can disrupt critical business applications and services relying on these databases. This can lead to operational downtime, loss of productivity, and potential financial losses. Since the vulnerability requires high privileges, the risk is elevated in environments where administrative access is not tightly controlled or where attackers have already gained elevated access through other means. Industries such as finance, telecommunications, healthcare, and e-commerce, which heavily depend on MySQL databases for transaction processing and data management, could experience significant service interruptions. Additionally, organizations providing cloud or managed database services in Europe could face reputational damage if their MySQL infrastructure is impacted. The lack of confidentiality or integrity impact reduces the risk of data breaches directly from this vulnerability, but availability disruptions can indirectly affect compliance with regulations like GDPR if service outages impact data access or processing. Overall, the threat underscores the importance of securing privileged access and maintaining robust incident response capabilities.

Mitigation Recommendations

1. Apply patches from Oracle immediately once they become available to address CVE-2024-20978. 2. Restrict network access to MySQL Server instances to trusted administrators only, using firewalls, VPNs, or network segmentation to limit exposure. 3. Enforce the principle of least privilege by ensuring only necessary users have high privileged access to MySQL servers. 4. Implement strong authentication and authorization controls for MySQL administrative accounts, including multi-factor authentication where possible. 5. Monitor MySQL server logs and performance metrics for signs of hangs, crashes, or unusual activity that could indicate exploitation attempts. 6. Use intrusion detection/prevention systems (IDS/IPS) to detect anomalous network traffic targeting MySQL protocols. 7. Regularly audit and review user privileges and network access policies to minimize the attack surface. 8. Develop and test incident response plans specifically for database availability incidents to reduce downtime impact. 9. Consider deploying MySQL high availability solutions or clustering to mitigate the impact of potential DoS attacks by enabling failover. 10. Stay informed through vendor advisories and threat intelligence feeds to respond quickly to emerging exploit techniques.

Need more detailed analysis?Get Pro

Technical Details

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

Threat ID: 690a474b6d939959c802238b

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

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

Last updated: 11/5/2025, 3:04:12 PM

Views: 1

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