CVE-2024-21230: Oracle MySQL Cluster · Easily exploitable vulnerability allows low privileged attacker with network access via multiple
Affects Oracle MySQL ClusterSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium · fixed in 9.0.2 : update Oracle MySQL Cluster when convenient.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.9% chance of exploitation in 30 days – higher than 60% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 9.0.2, 8.4.3, 8.0.40
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation 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.
What to do
Upgrade com.mysql/mysql-cluster to 9.0.2, 8.4.3 or 8.0.40.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Mavencom.mysql/mysql-clusterpkg:maven/com.mysql/mysql-clusterOther threats | Affected
| Fixed in
|
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 network access to MySQL Cluster instances by implementing strict firewall rules and network segmentation, allowing only trusted hosts and services to communicate with the database cluster. 3. Disable or limit exposure of unnecessary protocols and services that provide network access to MySQL Cluster to reduce the attack surface. 4. Monitor MySQL Cluster logs and system resource usage for abnormal patterns indicative of attempted resource exhaustion or crashes. 5. Implement rate limiting and connection throttling at network and application layers to mitigate potential DoS attempts. 6. Conduct regular security assessments and vulnerability scans to identify and remediate exposure of MySQL Cluster instances. 7. Employ intrusion detection/prevention systems (IDS/IPS) tuned to detect unusual traffic patterns targeting database services. 8. Maintain an incident response plan that includes procedures for handling database service outages and recovery.
Description
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). 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 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 hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 6.5 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).