# CVE-2021-46661: Denial of service in n/a

> An attacker can cause a MariaDB application crash by exploiting an unused common table expression in specific query processing functions.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Feb 2022
- **Updated:** 4 Aug 2024
- **Also known as:** ALPINE-CVE-2021-46661, AZL-8405, BIT-mariadb-2021-46661, BIT-mariadb-min-2021-46661, BIT-mysql-client-2021-46661, DEBIAN-CVE-2021-46661, GHSA-jj99-6883-93g3, UBUNTU-CVE-2021-46661

## What is CVE-2021-46661?

CVE-2021-46661 is a medium-severity denial of service vulnerability in Fedoraproject Fedora, published on 1 Feb 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

MariaDB through 10.5.9 allows an application crash in find_field_in_tables and find_order_in_list via an unused common table expression (CTE).

## Which versions are affected by CVE-2021-46661?

3 open source packages ship an affected version, including mariadb, mariadb-min and mysql-client. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mariadb` | Bitnami | From 10.2.0 | 10.2.43, 10.3.34, 10.4.24, 10.5.15, 10.6.7, 10.7.3 |
| `mariadb-min` | Bitnami | From 10.2.0 | 10.2.43, 10.3.34, 10.4.24, 10.5.15, 10.6.7, 10.7.3 |
| `mysql-client` | Bitnami | From 10.2.0 | 10.2.43, 10.3.34, 10.4.24, 10.5.15, 10.6.7, 10.7.3 |

Products: Fedoraproject Fedora, Mariadb Mariadb.

## How do I fix CVE-2021-46661?

Upgrade mariadb to a fixed version for your release line: 10.2.43, 10.3.34, 10.4.24 or 10.5.15.

## Is CVE-2021-46661 being exploited?

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

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-46661 and fix it if it is affected.

What it is: CVE-2021-46661 is a medium-severity denial of service vulnerability in Fedoraproject Fedora, published on 1 Feb 2022. 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-2021-46661 in the wild and no public exploit code.

Affected packages and fixed versions:
- mariadb (Bitnami): affected from 10.2.0; fixed in 10.2.43, 10.3.34, 10.4.24, 10.5.15, 10.6.7, 10.7.3
- mariadb-min (Bitnami): affected from 10.2.0; fixed in 10.2.43, 10.3.34, 10.4.24, 10.5.15, 10.6.7, 10.7.3
- mysql-client (Bitnami): affected from 10.2.0; fixed in 10.2.43, 10.3.34, 10.4.24, 10.5.15, 10.6.7, 10.7.3

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-2021-46661/ (Markdown: https://insights.sbomify.com/CVE-2021-46661/index.md)
```

## Sources

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

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