VulnerabilityPublished 16 Jan 2024Updated 2 Jun 2025

CVE-2024-20975: 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.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.8% chance of exploitation in 30 days – higher than 59% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Oracle Corporation MySQL Server	Affected *	Fixed in–

AI-suggested

To mitigate CVE-2024-20975, European organizations should: 1) Immediately verify the MySQL Server versions in use and prioritize upgrading to versions beyond 8.2.0 where the vulnerability is fixed once patches are released by Oracle. 2) Restrict network access to MySQL servers by implementing strict firewall rules and network segmentation, limiting access only to trusted hosts and services. 3) Enforce the principle of least privilege by reviewing and minimizing user privileges on MySQL servers, especially for accounts accessible over the network. 4) Monitor MySQL server logs and network traffic for unusual connection attempts or repeated crashes indicative of exploitation attempts. 5) Employ intrusion detection/prevention systems (IDS/IPS) tuned to detect anomalous MySQL traffic patterns. 6) Consider deploying rate limiting or connection throttling on MySQL interfaces to reduce the risk of DoS attacks. 7) Prepare incident response plans specifically addressing MySQL service outages to minimize downtime impact. 8) Stay informed on Oracle security advisories for official patches and apply them promptly once available.

Description

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 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).

Impact

For European organizations, the impact of CVE-2024-20975 is primarily the risk of service disruption due to denial-of-service attacks on MySQL databases. MySQL is widely used across various sectors including finance, healthcare, government, and e-commerce in Europe. A successful DoS attack could lead to downtime of critical applications relying on MySQL databases, causing operational disruption, loss of productivity, and potential financial losses. Although the vulnerability does not allow data theft or modification, the availability impact can affect business continuity and service level agreements (SLAs). Organizations with multi-tenant environments or those providing database-as-a-service could face amplified risks if attackers exploit this vulnerability to disrupt multiple customers. Additionally, sectors with stringent uptime requirements, such as banking and telecommunications, may experience reputational damage and regulatory scrutiny if service outages occur. The lack of known exploits in the wild currently reduces immediate risk, but the ease of exploitation and network accessibility mean that threat actors could develop exploits rapidly.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Jul 2025, 16:41 UTC

Technical details

References

Community reviews

Related threats