CVE-2024-20962: Oracle MySQL Server · Easily exploitable vulnerability allows low privileged attacker with network access via multiple
Affects Oracle MySQL ServerSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium : upgrade to 8.2.1 or 8.0.36 when convenient.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 1.1% chance of exploitation in 30 days – higher than 65% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 8.2.1, 8.0.36
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 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-26.
What to do
Upgrade mysql/mysql-server to 8.2.1 or 8.0.36.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Mysqlmysql/mysql-serverpkg:deb/mysql/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 closely for the release of security patches addressing CVE-2024-20962 and apply them immediately upon availability. 2. Restrict network access to MySQL Server instances by implementing strict firewall rules and network segmentation, allowing only trusted hosts and services to connect. 3. Disable or limit exposure of MySQL Server protocols that are not required, reducing the attack surface. 4. Implement robust monitoring and alerting on MySQL server performance and availability metrics to detect early signs of hangs or crashes. 5. Employ rate limiting or connection throttling mechanisms to mitigate potential resource exhaustion attacks. 6. Review and enforce least privilege principles for MySQL user accounts to minimize the impact of compromised credentials. 7. Consider deploying MySQL servers behind application-layer proxies or VPNs to add an additional layer of access control. 8. Conduct regular backups and have tested recovery procedures to minimize downtime impact in case of successful exploitation. 9. Educate IT and security teams about this vulnerability to ensure rapid incident response if exploitation attempts are detected.
Description
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.35 and prior and 8.2.0 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).