CVE-2024-20964: Oracle MySQL Server · Difficult to exploit vulnerability allows low privileged attacker with network access via multiple
Affects Oracle MySQL ServerSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 1.0% chance of exploitation in 30 days – higher than 63% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 17 Feb 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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Oracleoracle/mysql-serverpkg:rpm/oracle/mysql-serverOther 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. Monitor Oracle’s official channels for patches addressing CVE-2024-20964 and apply them promptly once released. 2. Restrict network access to MySQL Server instances by implementing strict firewall rules and network segmentation, limiting exposure to trusted hosts and internal networks only. 3. Disable or restrict unnecessary MySQL protocols and services that could be exploited to reduce the attack surface. 4. Implement resource limits and query throttling on MySQL to mitigate potential resource exhaustion scenarios. 5. Continuously monitor MySQL server logs and performance metrics for signs of hangs, crashes, or abnormal behavior indicative of exploitation attempts. 6. Employ intrusion detection systems (IDS) and anomaly detection tools tuned to detect unusual MySQL traffic patterns. 7. Ensure that MySQL user privileges follow the principle of least privilege to minimize potential attack vectors. 8. Consider deploying high availability and failover mechanisms to reduce service disruption impact in case of a DoS event. 9. Conduct regular security assessments and penetration tests focusing on MySQL server exposure and resilience against DoS attacks. 10. Educate system administrators and security teams about this vulnerability and the importance of timely patching and network controls.
Description
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Security: Privileges). Supported versions that are affected are 8.0.35 and prior and 8.2.0 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 hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 5.3 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H).