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-21237: Difficult to exploit 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 partial denial of service (partial DOS) of MySQL Server. in Oracle Corporation MySQL Server

0
Low
VulnerabilityCVE-2024-21237cvecve-2024-21237
Published: Tue Oct 15 2024 (10/15/2024, 19:52:47 UTC)
Source: CVE Database V5
Vendor/Project: Oracle Corporation
Product: MySQL Server

Description

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Group Replication GCS). Supported versions that are affected are 8.0.39 and prior, 8.4.2 and prior and 9.0.1 and prior. Difficult to exploit 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 partial denial of service (partial DOS) of MySQL Server. CVSS 3.1 Base Score 2.2 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L).

AI-Powered Analysis

AILast updated: 11/03/2025, 23:50:58 UTC

Technical Analysis

CVE-2024-21237 is a vulnerability identified in Oracle Corporation's MySQL Server, specifically within the Group Replication Global Communication System (GCS) component. It affects multiple supported versions, including 8.0.39 and earlier, 8.4.2 and earlier, and 9.0.1 and earlier. The vulnerability allows a high-privileged attacker who has network access through multiple protocols to compromise the MySQL Server by causing a partial denial of service (DoS). The attack complexity is high, meaning exploitation requires significant conditions or knowledge, and no user interaction is needed. The vulnerability impacts availability only, with no confidentiality or integrity compromise. The CVSS 3.1 base score is 2.2, indicating a low-severity issue primarily affecting service availability. No known exploits have been reported in the wild, and no patches were linked in the provided data, suggesting that organizations should remain vigilant for official updates. The partial DoS could degrade database service performance or availability, potentially disrupting applications relying on MySQL replication features. The vulnerability’s presence in the Group Replication GCS component suggests it could impact distributed MySQL setups that use group replication for high availability and fault tolerance.

Potential Impact

For European organizations, the primary impact of CVE-2024-21237 is a potential partial denial of service on MySQL Server instances, particularly those utilizing group replication features. This could lead to degraded database availability, affecting business-critical applications, especially in sectors like finance, telecommunications, and public services that rely heavily on MySQL for data management and replication. Although the vulnerability does not compromise data confidentiality or integrity, even partial service disruptions can cause operational delays, loss of productivity, and reputational damage. Organizations with high-privileged users having network access to MySQL servers are at greater risk. Given the difficulty of exploitation and the requirement for high privileges, the threat is less immediate but still warrants attention in environments where MySQL servers are exposed or insufficiently segmented. The lack of known exploits reduces immediate risk but does not eliminate the need for proactive mitigation.

Mitigation Recommendations

European organizations should implement the following specific mitigations: 1) Restrict network access to MySQL servers, especially limiting high-privileged user connections to trusted hosts and networks only. 2) Enforce the principle of least privilege by reviewing and minimizing high-privileged accounts with network access to MySQL. 3) Monitor MySQL server logs and network traffic for unusual activity related to group replication communications. 4) Apply network segmentation and firewall rules to isolate MySQL servers from untrusted networks. 5) Stay updated with Oracle’s security advisories and apply patches promptly once available. 6) Consider disabling group replication features if not required or temporarily suspending replication during investigation. 7) Conduct regular security audits and vulnerability scans focusing on database infrastructure. These targeted actions go beyond generic advice by focusing on the specific attack vector and component affected.

Need more detailed analysis?Get Pro

Technical Details

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

Threat ID: 6909261cfe7723195e0b38b0

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

Last enriched: 11/3/2025, 11:50:58 PM

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