Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-21262: Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise MySQL Connectors. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of MySQL Connectors accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of MySQL Connectors. in Oracle Corporation MySQL Connectors

0
Medium
VulnerabilityCVE-2024-21262cvecve-2024-21262
Published: Tue Oct 15 2024 (10/15/2024, 19:52:54 UTC)
Source: CVE Database V5
Vendor/Project: Oracle Corporation
Product: MySQL Connectors

Description

Vulnerability in the MySQL Connectors product of Oracle MySQL (component: Connector/ODBC). Supported versions that are affected are 9.0.0 and prior. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise MySQL Connectors. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of MySQL Connectors accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of MySQL Connectors. CVSS 3.1 Base Score 6.5 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L).

AI-Powered Analysis

AILast updated: 11/03/2025, 23:52:09 UTC

Technical Analysis

CVE-2024-21262 is a vulnerability in Oracle's MySQL Connectors, specifically the Connector/ODBC component, affecting all versions up to and including 9.0.0. The flaw allows an unauthenticated attacker with network access to exploit multiple protocols to gain unauthorized capabilities to update, insert, or delete data accessible via these connectors. This indicates a failure in proper access control mechanisms (CWE-863: Incorrect Authorization) within the connector software. The vulnerability also enables the attacker to cause a partial denial of service, impacting the availability of MySQL Connectors. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L) highlights that the attack can be launched remotely over the network with low complexity, no privileges, and no user interaction, affecting integrity and availability but not confidentiality. The absence of known exploits in the wild suggests it is newly disclosed, but the ease of exploitation and broad network accessibility make it a significant risk. The lack of currently available patches necessitates immediate risk mitigation through configuration and network controls. MySQL Connectors are widely used to facilitate database connectivity in various applications, making this vulnerability relevant for any organization relying on MySQL databases for critical operations.

Potential Impact

For European organizations, the vulnerability poses a risk of unauthorized data manipulation—such as unauthorized updates, inserts, or deletions—potentially compromising the integrity of business-critical data. This can lead to corrupted records, inaccurate reporting, or compromised transactional systems. The partial denial of service can disrupt application availability, affecting business continuity and service delivery. Sectors such as finance, healthcare, manufacturing, and public administration, which often rely on MySQL databases and connectors for backend data operations, are particularly vulnerable. The unauthenticated nature of the attack and network accessibility increase the risk of exploitation by external threat actors, including cybercriminals and state-sponsored groups. Given the interconnected nature of European IT infrastructures and regulatory requirements like GDPR, data integrity issues could also lead to compliance violations and reputational damage. The medium severity score reflects moderate but tangible risks that require prompt attention to avoid escalation or chained attacks.

Mitigation Recommendations

1. Immediate network-level controls: Restrict network access to MySQL Connectors by implementing firewall rules and network segmentation to limit exposure only to trusted hosts and internal networks. 2. Monitor and log all database connector traffic for unusual update, insert, or delete operations to detect potential exploitation attempts early. 3. Apply principle of least privilege on database accounts used by connectors to minimize the impact of unauthorized data manipulation. 4. Disable or restrict unused MySQL Connector protocols and interfaces to reduce the attack surface. 5. Stay updated with Oracle’s security advisories and apply patches as soon as they become available. 6. Conduct thorough security assessments and penetration testing focused on MySQL Connectors to identify and remediate any configuration weaknesses. 7. Employ intrusion detection/prevention systems (IDS/IPS) tuned to detect anomalous MySQL Connector activities. 8. Educate IT and security teams about this vulnerability and ensure incident response plans include scenarios involving database connector compromise. 9. Consider deploying Web Application Firewalls (WAFs) or database activity monitoring tools that can enforce stricter access controls and detect suspicious queries. 10. Review and update backup and recovery procedures to ensure rapid restoration in case of data integrity compromise or DoS incidents.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
oracle
Date Reserved
2023-12-07T22:28:10.702Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6909261dfe7723195e0b415e

Added to database: 11/3/2025, 10:01:01 PM

Last enriched: 11/3/2025, 11:52:09 PM

Last updated: 11/5/2025, 12:07:37 PM

Views: 1

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats