# CVE-2024-21096: Missing authorization in MySQL Server > An attacker with local access can compromise MySQL Server to read, modify, or delete data and cause partial denial of service. - **Severity:** Medium 4.9 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 16 Apr 2024 - **Updated:** 13 Feb 2025 - **Also known as:** ALPINE-CVE-2024-21096, ALSA-2025:0737, ALSA-2025:0912, AZL-49936, AZL-49948, AZL-49962, AZL-49971, BELL-CVE-2024-21096, BIT-mariadb-2024-21096, BIT-mariadb-min-2024-21096, BIT-mysql-client-2024-21096, DEBIAN-CVE-2024-21096, DLA-3891-1, GHSA-3vx9-2ch5-m6r6, MGASA-2024-0195, OESA-2025-1395, RHSA-2025:0737, RHSA-2025:0912, RLSA-2025:0737, RLSA-2025:0912, SUSE-SU-2024:2032-1, SUSE-SU-2024:3018-1, UBUNTU-CVE-2024-21096, USN-6839-1 ## What is CVE-2024-21096? CVE-2024-21096 is a medium-severity missing authorization vulnerability in Debian Debian Linux, published on 16 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description Vulnerability in the MySQL Server product of Oracle MySQL (component: Client: mysqldump). Supported versions that are affected are 8.0.36 and prior and 8.3.0 and prior. Difficult to exploit vulnerability allows unauthenticated attacker with logon to the infrastructure where MySQL Server executes to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of MySQL Server accessible data as well as unauthorized read access to a subset of MySQL Server accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L). ## Which versions are affected by CVE-2024-21096? 3 open source packages ship an affected version, including mariadb, mariadb-min and mysql-client. It affects 7 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `mariadb` | Bitnami | All versions | 10.5.25, 10.6.18, 10.11.8, 11.0.6, 11.1.5, 11.2.4, 11.4.2 | | `mariadb-min` | Bitnami | All versions | 11.4.7 | | `mysql-client` | Bitnami | All versions | 10.5.25, 10.6.18, 10.11.8, 11.0.6, 11.1.5, 11.2.4, 11.4.2 | | `Judy` | AlmaLinux:8 | All versions | 1.0.5-18.module_el8.10.0+3947+ac422511 | | `Judy` | AlmaLinux:8 | All versions | 1.0.5-18.module_el8.10.0+3955+6534edaf | | `Judy` | AlmaLinux:8 | All versions | 1.0.5-18.module_el8.8.0+3620+5d452900 | | `galera` | AlmaLinux:8 | All versions | 26.4.20-1.module_el8.10.0+3947+ac422511 | | `galera` | AlmaLinux:8 | All versions | 26.4.20-1.module_el8.10.0+3955+6534edaf | | `mariadb` | AlmaLinux:8 | All versions | 3:10.11.10-1.module_el8.10.0+3955+6534edaf | | `mariadb-backup` | AlmaLinux:8 | All versions | 3:10.11.10-1.module_el8.10.0+3955+6534edaf | | `mariadb-common` | AlmaLinux:8 | All versions | 3:10.11.10-1.module_el8.10.0+3955+6534edaf | | `mariadb-devel` | AlmaLinux:8 | All versions | 3:10.11.10-1.module_el8.10.0+3955+6534edaf | | `mariadb-embedded` | AlmaLinux:8 | All versions | 3:10.11.10-1.module_el8.10.0+3955+6534edaf | | `mariadb-embedded-devel` | AlmaLinux:8 | All versions | 3:10.11.10-1.module_el8.10.0+3955+6534edaf | | `mariadb-errmsg` | AlmaLinux:8 | All versions | 3:10.11.10-1.module_el8.10.0+3955+6534edaf | | `mariadb-gssapi-server` | AlmaLinux:8 | All versions | 3:10.11.10-1.module_el8.10.0+3955+6534edaf | | `mariadb-oqgraph-engine` | AlmaLinux:8 | All versions | 3:10.11.10-1.module_el8.10.0+3955+6534edaf | | `mariadb-pam` | AlmaLinux:8 | All versions | 3:10.11.10-1.module_el8.10.0+3955+6534edaf | | `mariadb-server` | AlmaLinux:8 | All versions | 3:10.11.10-1.module_el8.10.0+3955+6534edaf | | `mariadb-server-galera` | AlmaLinux:8 | All versions | 3:10.11.10-1.module_el8.10.0+3955+6534edaf | | `mariadb-server-utils` | AlmaLinux:8 | All versions | 3:10.11.10-1.module_el8.10.0+3955+6534edaf | | `mariadb-test` | AlmaLinux:8 | All versions | 3:10.11.10-1.module_el8.10.0+3955+6534edaf | | `galera` | AlmaLinux:9 | All versions | 26.4.20-1.module_el9.5.0+135+c9657a87 | | `mariadb` | AlmaLinux:9 | All versions | 3:10.11.10-1.module_el9.5.0+135+c9657a87 | | `mariadb-backup` | AlmaLinux:9 | All versions | 3:10.11.10-1.module_el9.5.0+135+c9657a87 | | `mariadb-common` | AlmaLinux:9 | All versions | 3:10.11.10-1.module_el9.5.0+135+c9657a87 | | `mariadb-devel` | AlmaLinux:9 | All versions | 3:10.11.10-1.module_el9.5.0+135+c9657a87 | | `mariadb-embedded` | AlmaLinux:9 | All versions | 3:10.11.10-1.module_el9.5.0+135+c9657a87 | | `mariadb-embedded-devel` | AlmaLinux:9 | All versions | 3:10.11.10-1.module_el9.5.0+135+c9657a87 | | `mariadb-errmsg` | AlmaLinux:9 | All versions | 3:10.11.10-1.module_el9.5.0+135+c9657a87 | | `mariadb-gssapi-server` | AlmaLinux:9 | All versions | 3:10.11.10-1.module_el9.5.0+135+c9657a87 | | `mariadb-oqgraph-engine` | AlmaLinux:9 | All versions | 3:10.11.10-1.module_el9.5.0+135+c9657a87 | | `mariadb-pam` | AlmaLinux:9 | All versions | 3:10.11.10-1.module_el9.5.0+135+c9657a87 | | `mariadb-server` | AlmaLinux:9 | All versions | 3:10.11.10-1.module_el9.5.0+135+c9657a87 | | `mariadb-server-galera` | AlmaLinux:9 | All versions | 3:10.11.10-1.module_el9.5.0+135+c9657a87 | | `mariadb-server-utils` | AlmaLinux:9 | All versions | 3:10.11.10-1.module_el9.5.0+135+c9657a87 | | `mariadb-test` | AlmaLinux:9 | All versions | 3:10.11.10-1.module_el9.5.0+135+c9657a87 | | `Judy` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.0.5-18.module+el8.10.0+21221+7bee72c1 | | `Judy-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.0.5-18.module+el8.10.0+21221+7bee72c1 | | `Judy-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.0.5-18.module+el8.10.0+21221+7bee72c1 | Products: Debian Debian Linux, Fedoraproject Fedora, Netapp Active Iq Unified Manager, Netapp Oncommand Insight, Netapp Oncommand Workflow Automation, Netapp Snapcenter, Oracle Mysql. ## How do I fix CVE-2024-21096? Upgrade mariadb to a fixed version for your release line: 10.5.25, 10.6.18, 10.11.8 or 11.0.6. ## Is CVE-2024-21096 being exploited? There is no known exploitation of CVE-2024-21096 in the wild and no public exploit code. ## Other vulnerabilities in Debian Debian Linux - [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild) - [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild) - [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild) - [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild) - [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-21096 and fix it if it is affected. What it is: CVE-2024-21096 is a medium-severity missing authorization vulnerability in Debian Debian Linux, published on 16 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-21096 in the wild and no public exploit code. Affected packages and fixed versions: - mariadb (Bitnami): affected all versions; fixed in 10.5.25, 10.6.18, 10.11.8, 11.0.6, 11.1.5, 11.2.4, 11.4.2 - mariadb-min (Bitnami): affected all versions; fixed in 11.4.7 - mysql-client (Bitnami): affected all versions; fixed in 10.5.25, 10.6.18, 10.11.8, 11.0.6, 11.1.5, 11.2.4, 11.4.2 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-21096/ (Markdown: https://insights.sbomify.com/CVE-2024-21096/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-21096 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-21096 - OSV: https://osv.dev/vulnerability/CVE-2024-21096 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-21096/ Summaries are generated and may contain mistakes; the official description above is the record.