# CVE-2024-21166: Missing authorization in MySQL Server

> High-privileged attackers can modify critical data or cause denial of service in MySQL Server via InnoDB component.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:H/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:** 16 Jul 2024
- **Updated:** 4 Nov 2025
- **Also known as:** AZL-50516, AZL-50538, GHSA-2q9x-hq7p-v7m6, UBUNTU-CVE-2024-21166

## What is CVE-2024-21166?

CVE-2024-21166 is a medium-severity missing authorization vulnerability in Oracle Mysql, published on 16 Jul 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Vulnerability in the MySQL Server product of Oracle MySQL (component: InnoDB).  Supported versions that are affected are 8.0.36 and prior and  8.3.0 and prior. Difficult to exploit vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server.  Successful attacks of this vulnerability can result in  unauthorized creation, deletion or modification access to critical data or all MySQL Server accessible data and unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 5.9 (Integrity and Availability impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:H).

Weakness: CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2024-21166?

It affects 1 product.


Products: Oracle Mysql.

## How do I fix CVE-2024-21166?

Apply the vendor's patch.

## Is CVE-2024-21166 being exploited?

There is no known exploitation of CVE-2024-21166 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-2024-21166 and fix it if it is affected.

What it is: CVE-2024-21166 is a medium-severity missing authorization vulnerability in Oracle Mysql, published on 16 Jul 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-21166 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-2024-21166/ (Markdown: https://insights.sbomify.com/CVE-2024-21166/index.md)
```

## Sources

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

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