CVE-2024-21243VulnerabilityPublished 15 Oct 2024Updated 3 Nov 2025

CVE-2024-21243: 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

CVSS 3.1 base score

2.2Low

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

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:N

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

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: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation 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.

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
Mavencom.oracle/mysql-server`pkg:maven/com.oracle/mysql-server`Other threats	Affected <=8.4.2 <=9.0.1	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. Upgrade MySQL Server to versions later than 8.4.2 and 9.0.1 once patches are released by Oracle to address this vulnerability. 2. Restrict network access to MySQL telemetry services using firewall rules and network segmentation to limit exposure only to trusted hosts and administrators. 3. Enforce the principle of least privilege by ensuring that only necessary users have high-level privileges on MySQL servers. 4. Monitor MySQL server logs and network traffic for unusual access patterns or telemetry data requests that could indicate exploitation attempts. 5. Disable telemetry features if not required, reducing the attack surface related to this component. 6. Implement strong authentication and access controls on MySQL servers to prevent unauthorized privilege escalation. 7. Stay updated with Oracle security advisories for patches and additional mitigation guidance. 8. Conduct regular vulnerability assessments and penetration testing focused on database servers to detect potential exploitation paths.

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).

Impact

For European organizations, the impact is primarily limited to unauthorized disclosure of some telemetry data from MySQL Servers running vulnerable versions. Although the confidentiality impact is low, organizations handling sensitive or regulated data should consider this exposure significant. The requirement for high privileges means that the vulnerability is more a concern in environments where internal threat actors or compromised administrators exist. The lack of integrity or availability impact reduces the risk of service disruption or data manipulation. However, unauthorized read access could aid attackers in reconnaissance or lateral movement within networks. Organizations in sectors such as finance, healthcare, and critical infrastructure that rely heavily on MySQL databases may face increased risk if telemetry data contains sensitive operational information. The vulnerability’s network accessibility via multiple protocols also means that perimeter defenses and network segmentation are critical to limit exposure. Given no known exploits exist, the immediate threat level is low, but proactive mitigation is recommended to prevent future exploitation.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Nov 2025, 23:51 UTC

Technical details

References

Community reviews

Related threats