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

Description

Vulnerability in the MySQL Server product of Oracle MySQL (component: InnoDB). Supported versions that are affected are 8.0.36 and prior and 8.3.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, 17:01:37 UTC

Technical Analysis

CVE-2024-21160 is a vulnerability identified in the InnoDB component of Oracle MySQL Server affecting versions 8.0.36 and earlier, as well as 8.3.0 and earlier. The flaw allows an attacker with high privileges and network access through multiple protocols to cause the MySQL Server to hang or crash repeatedly, resulting in a complete denial-of-service (DoS) condition. The vulnerability specifically impacts availability without compromising confidentiality or integrity. The CVSS 3.1 base score is 4.9, reflecting a medium severity primarily due to the requirement of high privileges (PR:H) and no user interaction (UI:N). The attack vector is network-based (AV:N), making it exploitable remotely by authorized users. The vulnerability does not require user interaction and affects the server’s ability to maintain service continuity. No public exploits have been reported to date, but the ease of causing a DoS condition makes it a concern for environments where MySQL Server availability is critical. The vulnerability underscores the risks of granting high privileges and exposing database services over networks without adequate controls. Oracle has published the vulnerability but no patch links are currently provided, indicating that organizations should monitor for updates and apply patches promptly once available.

Potential Impact

For European organizations, the primary impact of CVE-2024-21160 is the potential for denial-of-service attacks against MySQL Server instances, which could disrupt critical business applications relying on database availability. This can lead to operational downtime, loss of productivity, and potential financial losses, especially in sectors such as finance, telecommunications, e-commerce, and public services where MySQL is widely used. While the vulnerability does not allow data theft or modification, the inability to access database services can severely affect service delivery and customer trust. Organizations with multi-tenant environments or cloud-hosted MySQL instances may face cascading effects if the database becomes unresponsive. Additionally, the requirement for high privileges limits exploitation to insiders or attackers who have already compromised administrative credentials, emphasizing the importance of internal security controls. The disruption of MySQL services could also impact compliance with data availability regulations under GDPR and other European data protection frameworks.

Mitigation Recommendations

To mitigate CVE-2024-21160, European organizations should: 1) Monitor Oracle’s security advisories closely and apply patches or updates as soon as they become available to address this vulnerability. 2) Restrict network access to MySQL Server instances by implementing strict firewall rules and network segmentation, allowing only trusted administrative hosts and users to connect. 3) Enforce the principle of least privilege by limiting high-level MySQL user accounts and regularly auditing privileges to reduce the risk of misuse. 4) Employ robust authentication mechanisms such as multi-factor authentication (MFA) for administrative access to MySQL servers. 5) Implement monitoring and alerting for unusual MySQL server behavior, including frequent crashes or hangs, to detect potential exploitation attempts early. 6) Consider deploying failover and redundancy mechanisms for critical MySQL deployments to minimize downtime in case of DoS conditions. 7) Conduct regular security training for database administrators and IT staff to recognize and respond to potential insider threats or credential compromises. These measures collectively reduce the attack surface and improve resilience against DoS attacks exploiting this vulnerability.

Need more detailed analysis?Get Pro

Technical Details

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

Threat ID: 690a2de5f0ba78a050535eff

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

Last enriched: 11/4/2025, 5:01:37 PM

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