CVE-2024-21213VulnerabilityPublished 15 Oct 2024Updated 3 Nov 2025

CVE-2024-21213: Oracle MySQL Server · Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure

Affects Oracle MySQL ServerSource CVE Database V5

Not known to be exploited · CVSS 4.2 Medium : upgrade to 8.0.40 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.2Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 8.0.40

CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:N/I:N/A:H

Attack Vector: Local
Attack Complexity: Low
Privileges Required: High
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade mysql/mysql-server to 8.0.40.

Affected software

Product	Affected	Fixed in
Mysqlmysql/mysql-server`pkg:deb/mysql/mysql-server`Other threats	Affected <8.0.40	Fixed in 8.0.40

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. 2. Restrict high-privileged access to MySQL Server infrastructure strictly on a need-to-know basis and enforce strong authentication mechanisms such as multi-factor authentication (MFA) for administrative accounts. 3. Implement network segmentation to isolate database servers from general user environments, reducing the risk of unauthorized access. 4. Conduct regular user awareness training to reduce the risk of successful social engineering attacks that could trigger the required human interaction. 5. Monitor MySQL Server logs and system behavior for signs of unusual activity or repeated crashes to enable early detection of exploitation attempts. 6. Employ robust incident response plans that include procedures for rapid recovery from DoS conditions affecting database availability. 7. Use role-based access control (RBAC) and audit trails to track and limit privileged user actions. 8. Consider deploying MySQL Server in high-availability clusters or with failover mechanisms to minimize downtime impact.

Description

Vulnerability in the MySQL Server product of Oracle MySQL (component: InnoDB). Supported versions that are affected are 8.0.39 and prior, 8.4.2 and prior and 9.0.1 and prior. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where MySQL Server executes to compromise MySQL Server. Successful attacks require human interaction from a person other than the attacker. 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.2 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:N/I:N/A:H).

Impact

For European organizations, the primary impact of CVE-2024-21213 is the potential for denial-of-service attacks against critical MySQL Server databases. This can disrupt business operations, cause downtime in customer-facing applications, and impact data-driven decision-making processes. Sectors such as finance, healthcare, telecommunications, and government agencies that rely heavily on MySQL for transactional or operational databases may experience service outages, leading to financial losses, regulatory non-compliance, and reputational damage. The requirement for high privileges and user interaction limits the attack surface but does not eliminate risk, especially in environments with multiple administrators or where social engineering is feasible. The vulnerability could be exploited internally or by attackers who have gained elevated access, making insider threat mitigation and access controls critical. Additionally, repeated crashes may complicate incident response and recovery efforts, increasing operational costs.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Nov 2025, 23:48 UTC

Technical details

References

Community reviews

Related threats