CVE-2017-3323 in MySQL Cluster
Summary
by MITRE
Vulnerability in the MySQL Cluster component of Oracle MySQL (subcomponent: Cluster: General). Supported versions that are affected are 7.2.25 and earlier, 7.3.14 and earlier and 7.4.12 and earlier. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise MySQL Cluster. Successful attacks of this vulnerability can result in unauthorized ability to cause a partial denial of service (partial DOS) of MySQL Cluster. CVSS v3.0 Base Score 3.7 (Availability impacts).
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Analysis
by VulDB Data Team • 05/15/2026
The vulnerability identified as CVE-2017-3323 resides within the MySQL Cluster component of Oracle MySQL, specifically within the Cluster: General subcomponent. This issue affects multiple version ranges including 7.2.25 and earlier, 7.3.14 and earlier, and 7.4.12 and earlier, representing a significant exposure across several supported releases. The vulnerability's classification as difficult to exploit indicates that while the attack vector requires some technical skill or specific conditions, it remains a genuine threat to database infrastructure security. The CVSS v3.0 base score of 3.7 reflects a moderate severity level, primarily impacting system availability through partial denial of service conditions.
The technical flaw manifests as an insufficient input validation mechanism within the MySQL Cluster's handling of network protocols. This weakness allows unauthenticated attackers to establish network connections and potentially compromise the cluster's operational integrity. The vulnerability's impact is categorized as partial denial of service, meaning that successful exploitation can disrupt cluster operations without necessarily leading to complete system failure or data compromise. Attackers with network access via multiple protocols can leverage this vulnerability to impair cluster functionality, potentially affecting database availability and service continuity. The cluster's general nature suggests this issue impacts core operational components rather than specific features, amplifying its potential impact across the entire MySQL Cluster deployment.
The operational consequences of this vulnerability extend beyond simple service disruption, as MySQL Cluster deployments often support critical business applications and data processing workflows. Organizations utilizing affected versions may experience degraded performance or temporary unavailability of database services, potentially affecting multiple applications dependent on cluster functionality. The partial denial of service impact means that while complete system failure may not occur, the cluster's ability to process queries and maintain consistent service levels becomes compromised. This vulnerability particularly affects environments where MySQL Cluster serves as a foundational component for high-availability database solutions, potentially exposing organizations to operational downtime and revenue impact.
Mitigation strategies should prioritize immediate patching of affected versions to address the underlying input validation issues. Organizations should implement network segmentation and access controls to limit exposure to unauthorized network access, particularly at the cluster's network boundaries. Monitoring for unusual network activity patterns and implementing intrusion detection systems can help identify potential exploitation attempts. The vulnerability aligns with CWE-20, which addresses "Improper Input Validation," and falls under ATT&CK technique T1190 for "Exploit Public-Facing Application" and T1499 for "Endpoint Denial of Service." Regular security assessments and vulnerability scanning should be conducted to identify similar issues within the broader MySQL ecosystem, ensuring comprehensive protection against related threats. Organizations should also consider implementing redundant cluster configurations and robust backup procedures to minimize impact should exploitation occur despite preventive measures.