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-21166: 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 creation, deletion or modification access to critical data or all MySQL Server accessible data and unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. in Oracle Corporation MySQL Server

0
Medium
VulnerabilityCVE-2024-21166cvecve-2024-21166
Published: Tue Jul 16 2024 (07/16/2024, 22:40:05 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. 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 creation, deletion or modification access to critical data or all MySQL Server accessible data and unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 5.9 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:H).

AI-Powered Analysis

AILast updated: 11/04/2025, 17:02:31 UTC

Technical Analysis

CVE-2024-21166 is a vulnerability identified in the InnoDB storage engine component of Oracle MySQL Server, affecting versions up to 8.0.36 and 8.3.0. The flaw allows a high privileged attacker with network access via multiple protocols to compromise the MySQL Server. The vulnerability is difficult to exploit due to the requirement for high privileges and network access, and it does not require user interaction. Successful exploitation can result in unauthorized creation, deletion, or modification of critical data stored within MySQL databases, impacting data integrity. Additionally, the attacker can cause the MySQL Server to hang or crash repeatedly, resulting in a denial-of-service condition that affects availability. The CVSS 3.1 vector (AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:H) indicates network attack vector, high attack complexity, high privileges required, no user interaction, unchanged scope, no confidentiality impact, but high integrity and availability impact. The vulnerability is classified under CWE-285 (Improper Authorization), indicating that the flaw stems from inadequate enforcement of authorization checks. No patches or exploits are currently publicly available, but the risk remains significant for environments where MySQL Server is exposed to high privileged users over the network.

Potential Impact

For European organizations, this vulnerability poses a risk primarily to the integrity and availability of critical data managed by MySQL Server. Organizations in sectors such as finance, healthcare, government, and e-commerce that rely heavily on MySQL for transactional data and backend services could face unauthorized data manipulation or service outages. The denial-of-service potential could disrupt business operations, leading to downtime and loss of productivity. Although exploitation requires high privileges, insider threats or compromised administrative accounts could leverage this vulnerability to escalate damage. The lack of confidentiality impact reduces the risk of data leakage but does not mitigate the serious consequences of data tampering or service disruption. Given the widespread use of MySQL in Europe, the vulnerability could affect a broad range of enterprises, especially those with network-exposed database servers or insufficient network segmentation.

Mitigation Recommendations

European organizations should implement the following specific mitigations: 1) Restrict network access to MySQL Server instances to trusted administrators and internal networks only, using firewalls and network segmentation to minimize exposure. 2) Enforce the principle of least privilege by limiting administrative and high privileged user accounts to only those necessary for operational tasks. 3) Monitor and audit MySQL administrative activities and network access logs to detect unusual or unauthorized actions promptly. 4) Apply security hardening best practices for MySQL, including disabling unused protocols and services that could provide network access vectors. 5) Stay alert for official Oracle patches or updates addressing CVE-2024-21166 and prioritize timely deployment once available. 6) Consider deploying Web Application Firewalls (WAFs) or Intrusion Detection/Prevention Systems (IDS/IPS) capable of detecting anomalous MySQL traffic patterns. 7) Conduct regular security assessments and penetration testing focusing on database security controls to identify potential privilege escalation paths.

Need more detailed analysis?Get Pro

Technical Details

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

Threat ID: 690a2de5f0ba78a050535f0b

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

Last enriched: 11/4/2025, 5:02:31 PM

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