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

Description

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Security: Privileges). 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, 17:01:03 UTC

Technical Analysis

CVE-2024-21142 is a vulnerability in Oracle MySQL Server affecting versions 8.0.37 and earlier, as well as 8.4.0 and earlier. It resides in the server's privilege management component and allows a high-privileged attacker with network access to cause the server to hang or crash repeatedly, resulting in a complete denial-of-service (DoS) condition. The vulnerability can be exploited over multiple network protocols, increasing the attack surface. The CVSS 3.1 base score is 4.9, reflecting a medium severity primarily due to its impact on availability (no confidentiality or integrity impact). The attack requires the attacker to have high privileges on the MySQL Server, but no user interaction is needed. The underlying weakness is related to resource exhaustion (CWE-400), which suggests that the attacker can trigger conditions that consume excessive resources, leading to service disruption. No patches or exploits are currently publicly available, but the vulnerability is officially published and should be addressed promptly. This vulnerability does not allow data theft or modification but can disrupt services relying on MySQL, potentially affecting business continuity.

Potential Impact

For European organizations, the primary impact of CVE-2024-21142 is service disruption due to denial-of-service attacks on MySQL Server instances. Organizations that use MySQL for critical applications, databases, or backend services may experience outages or degraded performance, affecting availability of services to customers and internal users. 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 attackers have already gained elevated access, such as through insider threats or lateral movement after initial compromise. Industries with high reliance on database availability, such as finance, healthcare, e-commerce, and public sector services, are particularly vulnerable. Additionally, cloud service providers and managed service providers hosting MySQL databases in Europe could face cascading impacts if exploited. The lack of known exploits reduces immediate risk, but the ease of exploitation over network protocols means that once exploited, the impact can be widespread and disruptive.

Mitigation Recommendations

European organizations should implement the following specific mitigations: 1) Monitor and restrict high-privilege access to MySQL Server instances, ensuring the principle of least privilege is enforced. 2) Apply network segmentation and firewall rules to limit network access to MySQL servers only to trusted hosts and services. 3) Deploy intrusion detection and prevention systems (IDS/IPS) to detect unusual patterns indicative of resource exhaustion or DoS attempts targeting MySQL. 4) Regularly audit MySQL user privileges and remove unnecessary high-privilege accounts. 5) Prepare for patch deployment by tracking Oracle's security advisories and applying updates promptly once patches are released. 6) Implement resource limits and connection throttling on MySQL servers to mitigate potential resource exhaustion attacks. 7) Maintain robust backup and recovery procedures to minimize downtime impact. 8) Conduct penetration testing and vulnerability assessments focused on privilege escalation and DoS scenarios in MySQL environments. These steps go beyond generic advice by focusing on privilege management, network controls, and proactive monitoring tailored to this vulnerability's characteristics.

Need more detailed analysis?Get Pro

Technical Details

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

Threat ID: 690a2de5f0ba78a050535ef7

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

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

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