# CVE-2017-3321: Denial of service in MySQL Cluster

> An unauthenticated attacker can cause a partial denial of service in MySQL Cluster via network access.

- **Severity:** Low 3.7 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jan 2017
- **Updated:** 8 Oct 2024
- **Also known as:** GHSA-f52v-43r8-5wwj

## What is CVE-2017-3321?

CVE-2017-3321 is a low-severity denial of service vulnerability in Oracle Mysql Cluster, published on 27 Jan 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in the MySQL Cluster component of Oracle MySQL (subcomponent: Cluster: General). Supported versions that are affected are 7.2.19 and earlier, 7.3.8 and earlier and 7.4.5 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).

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2017-3321?

It affects 1 product.


Products: Oracle Mysql Cluster.

## How do I fix CVE-2017-3321?

No fix has been published for CVE-2017-3321 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-3321 being exploited?

There is no known exploitation of CVE-2017-3321 in the wild and no public exploit code.

## Other vulnerabilities in Oracle Mysql Cluster

- [CVE-2026-60163](https://insights.sbomify.com/CVE-2026-60163/): Privilege escalation in MySQL Cluster (high 8.4)
- [CVE-2026-60592](https://insights.sbomify.com/CVE-2026-60592/): Denial of service in MySQL Cluster (high 8.2)
- [CVE-2026-60315](https://insights.sbomify.com/CVE-2026-60315/): Information disclosure in MySQL Cluster (high 8.2)
- [CVE-2026-101772](https://insights.sbomify.com/CVE-2026-101772/): Vulnerability in the MySQL Server, MySQL Cluster product of Oracle MySQL (component: Client programs). (high 8.1)
- [CVE-2026-70724](https://insights.sbomify.com/CVE-2026-70724/): Auth bypass in MySQL Cluster (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-3321 and fix it if it is affected.

What it is: CVE-2017-3321 is a low-severity denial of service vulnerability in Oracle Mysql Cluster, published on 27 Jan 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-3321 in the wild and no public exploit code.

Affected product: Oracle Mysql Cluster. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-3321/ (Markdown: https://insights.sbomify.com/CVE-2017-3321/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-3321
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-3321
- OSV: https://osv.dev/vulnerability/CVE-2017-3321

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-3321/
Summaries are generated and may contain mistakes; the official description above is the record.