CVE-2024-21134VulnerabilityPublished 16 Jul 2024Updated 4 Nov 2025

CVE-2024-21134: 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 4.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.3Medium

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

EPSS: 0.7% chance of exploitation in 30 days – higher than 55% 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:L

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

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: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Jul 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.

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

1. Apply official Oracle patches promptly once they are released for the affected MySQL Server versions. 2. Restrict network access to MySQL ports (default 3306) using firewalls and network segmentation to limit exposure to trusted hosts only. 3. Implement strict access controls and monitor for unusual connection attempts or traffic patterns indicative of exploitation attempts. 4. Employ intrusion detection/prevention systems (IDS/IPS) tuned to detect anomalous MySQL traffic or partial DoS behaviors. 5. Regularly update and audit MySQL server configurations to minimize attack surface, disabling unused protocols or features. 6. Consider deploying rate limiting or connection throttling mechanisms to mitigate potential DoS effects. 7. Maintain up-to-date backups and incident response plans to quickly recover from service disruptions. 8. Conduct internal vulnerability scans and penetration tests to identify exposure to this and related vulnerabilities. 9. Educate system administrators about this vulnerability and the importance of timely patching and network hygiene. 10. Monitor threat intelligence feeds for emerging exploit information to adjust defenses accordingly.

Description

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Connection Handling). Supported versions that are affected are 8.0.37 and prior and 8.4.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 partial denial of service (partial DOS) of MySQL Server. CVSS 3.1 Base Score 4.3 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L).

Impact

For European organizations, the primary impact of CVE-2024-21134 is the potential for partial denial of service on MySQL Server instances. This can lead to degraded performance or temporary unavailability of database services, affecting business-critical applications such as e-commerce platforms, financial services, and public sector systems that rely on MySQL. While the vulnerability does not allow data theft or modification, service interruptions can cause operational disruptions, loss of productivity, and reputational damage. Organizations with MySQL servers exposed to untrusted networks or insufficiently segmented internal networks are at higher risk. The partial DoS could also complicate incident response and recovery efforts. Given the widespread use of MySQL across Europe in various sectors, the threat could have a broad impact, especially in industries with high availability requirements. The absence of known exploits reduces immediate risk but does not eliminate the threat, as attackers may develop exploits once details become widely known.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2025, 17:00 UTC

Technical details

References

Community reviews

Related threats