# CVE-2016-3424: Denial of service in n/a

> Remote administrators can cause a denial of service in MySQL Server via unspecified vectors related to the Optimizer.

- **Severity:** Medium 4.9 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Jul 2016
- **Updated:** 11 Oct 2024
- **Also known as:** GHSA-w6v5-5mgv-7pgm, UBUNTU-CVE-2016-3424

## What is CVE-2016-3424?

CVE-2016-3424 is a medium-severity denial of service vulnerability in Oracle Mysql, published on 21 Jul 2016. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Unspecified vulnerability in Oracle MySQL 5.7.12 and earlier allows remote administrators to affect availability via vectors related to Server: Optimizer.

## Which versions are affected by CVE-2016-3424?

It affects 1 product.


Products: Oracle Mysql.

## How do I fix CVE-2016-3424?

Upgrade to a fixed version.

## Is CVE-2016-3424 being exploited?

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

## Other vulnerabilities in Oracle Mysql

- [CVE-2016-0639](https://insights.sbomify.com/CVE-2016-0639/): Auth bypass in n/a (critical 9.8)
- [CVE-2003-0150](https://insights.sbomify.com/CVE-2003-0150/): Privilege escalation in n/a (critical 9.0)
- [CVE-2005-2572](https://insights.sbomify.com/CVE-2005-2572/): Denial of service in n/a (high 8.5)
- [CVE-2020-14878](https://insights.sbomify.com/CVE-2020-14878/): Auth bypass in MySQL Server (high 8.0)
- [CVE-2002-0969](https://insights.sbomify.com/CVE-2002-0969/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-3424 and fix it if it is affected.

What it is: CVE-2016-3424 is a medium-severity denial of service vulnerability in Oracle Mysql, published on 21 Jul 2016. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-3424 in the wild and no public exploit code.

Affected product: Oracle Mysql. 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-2016-3424/ (Markdown: https://insights.sbomify.com/CVE-2016-3424/index.md)
```

## Sources

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

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