CVE-2017-3323: Oracle MySQL Cluster vulnerability

CVE-2017-3323: Vulnerability in the MySQL Cluster component of Oracle MySQL (subcomponent: Cluster: General).

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

UnknownCVSS not scoredNot KEV-listedUpdatedOct 8, 2024, 20:28 UTC (UTC+00:00)

Security readout for executives and security teams

CVE-2017-3323 is an Oracle MySQL Cluster flaw that can let an unauthenticated network attacker cause partial service disruption. The reported impact is availability only, with CVSS v3.0 score 3.7. It matters most where affected MySQL Cluster versions support business-critical workloads and cluster services are reachable from untrusted networks. Exposure is likely limited to organizations running affected MySQL Cluster 7.2, 7.3, or 7.4 releases with cluster network services accessible to an attacker. Treat this as a low-to-moderate operational risk, not a breach emergency. Remediate during normal patch cycles unless affected clusters are externally reachable or support critical services, where availability disruption could have business impact. Mitigation focus: Identify any Oracle MySQL Cluster deployments and versions.; Apply Oracle's January 2017 Critical Patch Update or current vendor guidance for MySQL Cluster.; Restrict network access to MySQL Cluster services to trusted systems only..

Prepared: Jun 13, 2026, 12:51 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2017-3323 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Jan 27, 2017, 22:01 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

1Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

OracleMySQL Cluster7.2.25 and earlier, 7.3.14 and earlier, 7.4.12 and earlierListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.