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-21127: 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-21127cvecve-2024-21127
Published: Tue Jul 16 2024 (07/16/2024, 22:39:52 UTC)
Source: CVE Database V5
Vendor/Project: Oracle Corporation
Product: MySQL Server

Description

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: DDL). Supported versions that are affected are 8.0.37 and prior and 8.4.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, 16:59:38 UTC

Technical Analysis

CVE-2024-21127 is a denial-of-service vulnerability identified in Oracle MySQL Server, specifically affecting versions 8.0.37 and earlier, as well as 8.4.0 and earlier. The flaw resides in the Server: DDL component, which handles Data Definition Language operations. A high privileged attacker with network access via multiple protocols can exploit this vulnerability to cause the MySQL Server to hang or crash repeatedly, resulting in a complete denial-of-service condition. The CVSS 3.1 base score is 4.9, reflecting 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 vulnerability does not affect confidentiality or integrity, only availability (A:H). No known exploits have been reported in the wild as of the publication date. The underlying weakness is categorized under CWE-400, which relates to uncontrolled resource consumption leading to DoS. The vulnerability is easily exploitable by an attacker who already has high privileges on the network, potentially through compromised credentials or lateral movement within a network. The absence of patches at the time of reporting necessitates immediate attention to network segmentation and access controls to mitigate risk.

Potential Impact

For European organizations, this vulnerability poses a risk of service disruption in environments using affected MySQL Server versions. Critical business applications, websites, and data services relying on MySQL databases could experience outages, impacting operational continuity and potentially causing financial and reputational damage. Sectors such as finance, healthcare, telecommunications, and government that depend heavily on database availability are particularly vulnerable. Although the vulnerability does not allow data theft or manipulation, the denial-of-service could be leveraged as part of a broader attack strategy to distract or degrade defenses. The requirement for high privileges limits the attack surface but also indicates that insider threats or attackers who have already breached perimeter defenses could exploit this vulnerability. The lack of known exploits reduces immediate risk but does not eliminate the threat, especially as exploit code could emerge following public disclosure.

Mitigation Recommendations

Organizations should prioritize upgrading MySQL Server to versions beyond 8.0.37 and 8.4.0 once Oracle releases patches addressing CVE-2024-21127. Until patches are available, restrict network access to MySQL servers by implementing strict firewall rules and network segmentation to limit exposure to only trusted hosts and services. Employ strong authentication and authorization controls to minimize the risk of privilege escalation that could enable exploitation. Monitor MySQL server logs and network traffic for unusual activity indicative of attempts to trigger hangs or crashes. Consider deploying rate limiting or connection throttling to reduce the impact of potential resource exhaustion attacks. Regularly review and update incident response plans to include scenarios involving database DoS conditions. Additionally, conduct internal audits to ensure no unnecessary high privileged accounts exist and enforce the principle of least privilege. Engage with Oracle support channels to receive timely updates and advisories.

Need more detailed analysis?Get Pro

Technical Details

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

Threat ID: 690a2de3f0ba78a050535d00

Added to database: 11/4/2025, 4:46:27 PM

Last enriched: 11/4/2025, 4:59:38 PM

Last updated: 11/5/2025, 2:21:15 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