CVE-2025-30710
📋 TL;DR
This vulnerability in Oracle MySQL Cluster allows high-privileged attackers with network access to cause denial of service by crashing or hanging the MySQL Cluster service. It affects MySQL Cluster versions 8.0.0-8.0.41, 8.4.0-8.4.4, and 9.0.0-9.2.0. Only attackers with administrative database privileges can exploit this vulnerability.
💻 Affected Systems
- Oracle MySQL Cluster
- MySQL NDBCluster Plugin
📦 What is this software?
⚠️ Risk & Real-World Impact
Worst Case
Complete unavailability of MySQL Cluster service, disrupting all dependent applications and services.
Likely Case
Targeted DoS attacks by malicious insiders or compromised admin accounts causing service disruption.
If Mitigated
Minimal impact if proper access controls and network segmentation are implemented.
🎯 Exploit Status
Exploitation requires admin credentials but is described as 'easily exploitable' by Oracle.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: Versions after 8.0.41, 8.4.4, and 9.2.0
Vendor Advisory: https://www.oracle.com/security-alerts/cpuapr2025.html
Restart Required: Yes
Instructions:
1. Download latest patched version from Oracle. 2. Backup databases. 3. Stop MySQL Cluster services. 4. Apply patch/upgrade. 5. Restart services. 6. Verify functionality.
🔧 Temporary Workarounds
Restrict Network Access
linuxLimit network access to MySQL Cluster to only trusted administrative networks
iptables -A INPUT -p tcp --dport 1186 -s trusted_network -j ACCEPT
iptables -A INPUT -p tcp --dport 1186 -j DROP
Reduce Admin Privileges
allImplement least privilege principle for database accounts
REVOKE ALL PRIVILEGES ON *.* FROM 'admin_user'@'%';
GRANT SELECT, INSERT, UPDATE, DELETE ON specific_db.* TO 'admin_user'@'specific_host';
🧯 If You Can't Patch
- Implement strict network segmentation to isolate MySQL Cluster from untrusted networks
- Enforce multi-factor authentication and monitoring for all admin database accounts
🔍 How to Verify
Check if Vulnerable:
Check MySQL version: SELECT VERSION(); and verify if within affected ranges for Cluster edition
Check Version:
mysql -u root -p -e "SELECT VERSION();"
Verify Fix Applied:
Verify version is above affected ranges and test cluster functionality
📡 Detection & Monitoring
Log Indicators:
- Unexpected cluster shutdowns
- Connection attempts from unusual admin accounts
- Multiple failed cluster restart attempts
Network Indicators:
- Unusual traffic patterns to cluster management ports (1186)
- Multiple connection attempts from single source
SIEM Query:
source="mysql.log" ("shutdown" OR "crash" OR "restart") AND "cluster"