Skip to main content
CVE-2024-20984VulnerabilityPublished Updated

CVE-2024-20984: Oracle MySQL Server · Difficult to exploit vulnerability allows high privileged attacker with network access via multiple

Affects Oracle MySQL ServerSource CVE Database V5

0

Not known to be exploited · CVSS 4.4 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
4.4Medium
How severe the flaw is on the 0–10 CVSS scale.
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:H/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Feb 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Oracle Corporation MySQL ServerAffected
  • *
Fixed in–

AI-suggested

1. Apply patches promptly once Oracle releases official updates addressing CVE-2024-20984. Monitor Oracle security advisories closely. 2. Restrict network access to MySQL Server instances, especially limiting high privileged user access to trusted networks and IP addresses only. 3. Enforce the principle of least privilege by auditing and minimizing high privilege accounts with network access to MySQL. 4. Implement network segmentation and firewall rules to reduce exposure of MySQL services to untrusted networks. 5. Monitor MySQL server logs and system performance metrics for signs of hangs or crashes that could indicate exploitation attempts. 6. Employ intrusion detection/prevention systems (IDS/IPS) to detect anomalous network activity targeting MySQL protocols. 7. Conduct regular security reviews of MySQL configurations, ensuring that security firewall components are properly configured and up to date. 8. Prepare incident response plans specifically for database availability disruptions to minimize downtime impact. 9. Consider deploying MySQL high availability solutions (e.g., clustering, replication) to mitigate service disruption risks. 10. Educate privileged users on secure access practices and the risks associated with network exposure of critical database services.

Description

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server : Security : Firewall). Supported versions that are affected are 8.0.35 and prior and 8.2.0 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 ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.4 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H).

References

Community reviews

Loading reviews…