CVE-2024-21244: Oracle MySQL Server · Difficult to exploit vulnerability allows high privileged attacker with network access via multiple
Affects Oracle MySQL ServerSource CVE Database V5
Not known to be exploited · CVSS 2.2 Low.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:N/A:NExploitation 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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Mavencom.oracle/mysql-serverpkg:maven/com.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. Restrict network access to MySQL servers, especially limiting high-privilege user connections to trusted hosts and networks only. 2. Enforce the principle of least privilege by auditing and minimizing high-privilege accounts that can access MySQL over the network. 3. Monitor telemetry data flows and logs for unusual access patterns or unauthorized read attempts. 4. Apply Oracle's security patches promptly once they are released for the affected MySQL versions. 5. Use network segmentation and firewall rules to isolate MySQL servers from untrusted networks. 6. Implement strong authentication and encryption for MySQL connections to reduce risk of credential compromise. 7. Regularly review and update MySQL server configurations to disable unnecessary telemetry features if possible. 8. Conduct internal penetration testing focusing on privilege escalation and network access controls around MySQL servers. 9. Maintain up-to-date asset inventories to identify all MySQL instances and their versions for targeted patching. 10. Educate administrators about the risks of high-privilege network access and encourage adherence to security best practices.
Description
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Telemetry). Supported versions that are affected are 8.4.2 and prior and 9.0.1 and prior. Difficult to exploit vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized read access to a subset of MySQL Server accessible data. CVSS 3.1 Base Score 2.2 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:N/A:N).