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-21231: Difficult to exploit vulnerability allows low 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-21231cvecve-2024-21231
Published: Tue Oct 15 2024 (10/15/2024, 19:52:45 UTC)
Source: CVE Database V5
Vendor/Project: Oracle Corporation
Product: MySQL Server

Description

Vulnerability in the MySQL Server product of Oracle MySQL (component: Client programs). 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 low 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 3.1 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L).

AI-Powered Analysis

AILast updated: 11/03/2025, 23:49:56 UTC

Technical Analysis

CVE-2024-21231 is a vulnerability identified in Oracle MySQL Server, specifically within the client programs component, affecting multiple versions including 8.0.39 and prior, 8.4.2 and prior, and 9.0.1 and prior. The vulnerability allows an attacker with low privileges and network access through multiple protocols to compromise the MySQL Server by causing a partial denial of service (DoS). The root cause is related to resource exhaustion (CWE-400), where the server can be overwhelmed or destabilized by crafted network requests, leading to degraded availability. The attack complexity is high, meaning exploitation requires specific conditions or knowledge, and no user interaction is needed. The CVSS 3.1 base score is 3.1, reflecting a low severity primarily due to the limited impact on availability and the difficulty of exploitation. The vulnerability does not affect confidentiality or integrity of data. No known exploits have been reported in the wild, and no patches were listed at the time of publication, indicating that Oracle may be preparing or has recently released mitigations. The vulnerability affects multiple protocols used by MySQL Server, increasing the potential attack surface but still constrained by the high complexity and low impact.

Potential Impact

For European organizations, the primary impact of CVE-2024-21231 is the potential for partial denial of service on MySQL Server instances, which could disrupt database availability and affect dependent applications and services. This may lead to temporary service degradation or outages, impacting business operations reliant on MySQL databases. Since the vulnerability does not compromise data confidentiality or integrity, the risk of data breaches is minimal. However, availability issues can affect critical services, especially in sectors like finance, healthcare, and public administration where MySQL is widely used. The difficulty of exploitation and the requirement for network access reduce the likelihood of widespread attacks, but targeted attempts could still disrupt services. Organizations with exposed MySQL servers or those using multiple protocols for database access should be particularly cautious. The absence of known exploits in the wild lowers immediate risk but does not eliminate the need for vigilance.

Mitigation Recommendations

European organizations should implement the following specific mitigations: 1) Restrict network access to MySQL servers by enforcing strict firewall rules and network segmentation to limit exposure to trusted hosts and networks only. 2) Monitor MySQL server logs and network traffic for unusual or excessive connection attempts that could indicate exploitation attempts. 3) Apply Oracle's security patches promptly once available, as the current information indicates no patch links but updates may be released soon. 4) Disable or restrict unused MySQL protocols and client programs to reduce the attack surface. 5) Employ resource limits and connection throttling on MySQL servers to mitigate potential resource exhaustion attacks. 6) Conduct regular vulnerability assessments and penetration tests focusing on MySQL infrastructure to identify and remediate weaknesses. 7) Maintain up-to-date backups and incident response plans to quickly recover from potential service disruptions.

Need more detailed analysis?Get Pro

Technical Details

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

Threat ID: 6909261cfe7723195e0b389f

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

Last enriched: 11/3/2025, 11:49:56 PM

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