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-21241: 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-21241cvecve-2024-21241
Published: Tue Oct 15 2024 (10/15/2024, 19:52:48 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.39 and prior, 8.4.2 and prior and 9.0.1 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/03/2025, 23:51:28 UTC

Technical Analysis

CVE-2024-21241 is a vulnerability in the Oracle MySQL Server's Optimizer component affecting multiple supported versions including 8.0.39 and prior, 8.4.2 and prior, and 9.0.1 and prior. The flaw allows an attacker with high privileges and network access to exploit the server via multiple protocols to cause a denial-of-service condition by hanging or repeatedly crashing the MySQL Server process. The vulnerability does not compromise confidentiality or integrity but impacts availability, as indicated by its CVSS 3.1 base score of 4.9. The attack vector is network-based (AV:N), requires low attack complexity (AC:L), and high privileges (PR:H), with no user interaction needed (UI:N). The scope remains unchanged (S:U), meaning the impact is confined to the vulnerable component. Although no exploits are currently known in the wild, the ease of exploitation and potential for service disruption make this a significant concern for environments relying on MySQL for critical database operations. The vulnerability highlights the importance of controlling privileged access and network exposure of database servers. Oracle has published the vulnerability details but no patch links were provided at the time of this report, indicating that organizations should monitor for updates and apply patches promptly once available.

Potential Impact

For European organizations, the primary impact of CVE-2024-21241 is the potential for denial-of-service attacks against MySQL Server instances, leading to service outages and operational disruptions. This can affect any service or application relying on MySQL databases, including web services, internal business applications, and critical infrastructure systems. The availability impact can cause downtime, loss of productivity, and potential financial losses. Since the vulnerability requires high privileges, the risk is heightened in environments where privileged user accounts are exposed or where network segmentation is weak. Industries such as finance, telecommunications, government, and e-commerce in Europe, which heavily depend on MySQL for backend data storage, could face significant operational risks. Additionally, disruption of MySQL services could indirectly affect compliance with data availability requirements under regulations like GDPR if service outages impact data accessibility.

Mitigation Recommendations

To mitigate CVE-2024-21241, European organizations should: 1) Immediately identify and inventory all MySQL Server instances running affected versions (8.0.39 and prior, 8.4.2 and prior, 9.0.1 and prior). 2) Apply official Oracle patches as soon as they become available; monitor Oracle security advisories closely. 3) Restrict network access to MySQL servers by implementing strict firewall rules and network segmentation, allowing only trusted hosts and services to connect. 4) Limit the number of users with high privileges on MySQL servers and enforce the principle of least privilege. 5) Monitor MySQL server logs and system metrics for signs of hangs, crashes, or unusual activity indicative of exploitation attempts. 6) Consider deploying intrusion detection/prevention systems (IDS/IPS) tuned to detect anomalous MySQL traffic patterns. 7) Regularly back up databases to enable rapid recovery in case of service disruption. 8) Conduct security awareness training for administrators managing MySQL servers to recognize and respond to potential exploitation attempts.

Need more detailed analysis?Get Pro

Technical Details

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

Threat ID: 6909261cfe7723195e0b38b8

Added to database: 11/3/2025, 10:01:00 PM

Last enriched: 11/3/2025, 11:51:28 PM

Last updated: 11/5/2025, 3:45:56 PM

Views: 3

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