CVE-2024-20969: Oracle MySQL Server · Easily exploitable vulnerability allows high privileged attacker with network access via multiple
Affects Oracle MySQL ServerSource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:HExploitation evidence
Disclosed: evidence found.
CVE published 16 Jan 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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Oracle Corporation MySQL Server | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2024-20969 effectively, European organizations should: 1) Immediately review and restrict high-privileged network access to MySQL Server instances, implementing strict network segmentation and firewall rules to limit exposure. 2) Enforce the principle of least privilege by auditing and minimizing administrative accounts and their permissions on MySQL servers. 3) Monitor MySQL server logs and network traffic for unusual activity indicative of exploitation attempts, such as repeated crashes or unauthorized data modification commands. 4) Apply any available vendor patches or updates as soon as they are released by Oracle; in the absence of patches, consider temporary workarounds such as disabling vulnerable features or protocols if feasible. 5) Implement strong authentication mechanisms and consider multi-factor authentication for administrative access to reduce the risk of credential compromise. 6) Regularly back up MySQL databases and test restoration procedures to ensure data recovery in case of integrity violations or service disruption. 7) Conduct vulnerability scanning and penetration testing focused on MySQL servers to identify and remediate potential exploitation paths. These steps go beyond generic advice by focusing on access control, monitoring, and operational resilience specific to the vulnerability's characteristics.
Description
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: DDL). Supported versions that are affected are 8.0.35 and prior and 8.2.0 and prior. Easily exploitable vulnerability allows high 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 as well as unauthorized update, insert or delete access to some of MySQL Server accessible data. CVSS 3.1 Base Score 5.5 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:H).