# CVE-2021-27928: Code injection in n/a

> A database SUPER user can execute OS commands via eval injection in MariaDB by modifying specific configuration parameters.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/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:** 19 Mar 2021
- **Updated:** 3 Aug 2024
- **Also known as:** ALPINE-CVE-2021-27928, ALSA-2021:1242, BIT-mariadb-2021-27928, BIT-mariadb-min-2021-27928, BIT-mysql-client-2021-27928, DEBIAN-CVE-2021-27928, DLA-2605-1, GHSA-2q7x-w5q3-rjxc, MINI-jqpw-hxh5-7q33, MINI-rwhc-r5fm-rcf5, RHSA-2021:1039, RHSA-2021:1240, RHSA-2021:1241, RHSA-2021:1242, RHSA-2021:2040, RLSA-2021:1242, UBUNTU-CVE-2021-27928

## What is CVE-2021-27928?

CVE-2021-27928 is a high-severity code injection vulnerability in Debian Debian Linux, published on 19 Mar 2021. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A remote code execution issue was discovered in MariaDB 10.2 before 10.2.37, 10.3 before 10.3.28, 10.4 before 10.4.18, and 10.5 before 10.5.9; Percona Server through 2021-03-03; and the wsrep patch through 2021-03-03 for MySQL. An untrusted search path leads to eval injection, in which a database SUPER user can execute OS commands after modifying wsrep_provider and wsrep_notify_cmd. NOTE: this does not affect an Oracle product.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mariadb` | Bitnami | From 10.2.0 | 10.2.37, 10.3.28, 10.4.18, 10.5.9 |
| `mariadb-min` | Bitnami | From 10.2.0 | 10.2.37, 10.3.28, 10.4.18, 10.5.9 |
| `mysql-client` | Bitnami | From 10.2.0 | 10.2.37, 10.3.28, 10.4.18, 10.5.9 |
| `Judy` | AlmaLinux:8 | All versions | 1.0.5-18.module_el8.3.0+2028+5e3224e9 |
| `Judy` | AlmaLinux:8 | All versions | 1.0.5-18.module_el8.5.0+2632+14ced695 |
| `Judy` | AlmaLinux:8 | All versions | 1.0.5-18.module_el8.6.0+2761+593e5e59 |
| `Judy` | AlmaLinux:8 | All versions | 1.0.5-18.module_el8.6.0+2867+72759d2f |
| `Judy-devel` | AlmaLinux:8 | All versions | 1.0.5-18.module_el8.3.0+2028+5e3224e9 |
| `Judy-devel` | AlmaLinux:8 | All versions | 1.0.5-18.module_el8.6.0+2867+72759d2f |
| `Judy-devel` | AlmaLinux:8 | All versions | 1.0.5-18.module_el8.6.0+3072+3c630e87 |
| `asio-devel` | AlmaLinux:8 | All versions | 1.10.8-7.module_el8.6.0+2867+72759d2f |
| `asio-devel` | AlmaLinux:8 | All versions | 1.10.8-7.module_el8.6.0+3072+3c630e87 |
| `galera` | AlmaLinux:8 | All versions | 25.3.32-1.module_el8.3.0+2177+7adc332a |
| `mariadb` | AlmaLinux:8 | All versions | 3:10.3.28-1.module_el8.3.0+2177+7adc332a |
| `mariadb-backup` | AlmaLinux:8 | All versions | 3:10.3.28-1.module_el8.3.0+2177+7adc332a |
| `mariadb-common` | AlmaLinux:8 | All versions | 3:10.3.28-1.module_el8.3.0+2177+7adc332a |
| `mariadb-devel` | AlmaLinux:8 | All versions | 3:10.3.28-1.module_el8.3.0+2177+7adc332a |
| `mariadb-embedded` | AlmaLinux:8 | All versions | 3:10.3.28-1.module_el8.3.0+2177+7adc332a |
| `mariadb-embedded-devel` | AlmaLinux:8 | All versions | 3:10.3.28-1.module_el8.3.0+2177+7adc332a |
| `mariadb-errmsg` | AlmaLinux:8 | All versions | 3:10.3.28-1.module_el8.3.0+2177+7adc332a |
| `mariadb-gssapi-server` | AlmaLinux:8 | All versions | 3:10.3.28-1.module_el8.3.0+2177+7adc332a |
| `mariadb-oqgraph-engine` | AlmaLinux:8 | All versions | 3:10.3.28-1.module_el8.3.0+2177+7adc332a |
| `mariadb-server` | AlmaLinux:8 | All versions | 3:10.3.28-1.module_el8.3.0+2177+7adc332a |
| `mariadb-server-galera` | AlmaLinux:8 | All versions | 3:10.3.28-1.module_el8.3.0+2177+7adc332a |
| `mariadb-server-utils` | AlmaLinux:8 | All versions | 3:10.3.28-1.module_el8.3.0+2177+7adc332a |
| `mariadb-test` | AlmaLinux:8 | All versions | 3:10.3.28-1.module_el8.3.0+2177+7adc332a |
| `Judy` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.0.5-18.module+el8+2765+cfa4f87b |
| `Judy-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.0.5-18.module+el8+2765+cfa4f87b |
| `Judy-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.0.5-18.module+el8+2765+cfa4f87b |
| `galera` | Red Hat:enterprise_linux:8::appstream | All versions | 0:25.3.32-1.module+el8.3.0+10472+7adc332a |
| `galera-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:25.3.32-1.module+el8.3.0+10472+7adc332a |
| `galera-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:25.3.32-1.module+el8.3.0+10472+7adc332a |
| `mariadb` | Red Hat:enterprise_linux:8::appstream | All versions | 3:10.3.28-1.module+el8.3.0+10472+7adc332a |
| `mariadb-backup` | Red Hat:enterprise_linux:8::appstream | All versions | 3:10.3.28-1.module+el8.3.0+10472+7adc332a |
| `mariadb-backup-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 3:10.3.28-1.module+el8.3.0+10472+7adc332a |
| `mariadb-common` | Red Hat:enterprise_linux:8::appstream | All versions | 3:10.3.28-1.module+el8.3.0+10472+7adc332a |
| `mariadb-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 3:10.3.28-1.module+el8.3.0+10472+7adc332a |
| `mariadb-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 3:10.3.28-1.module+el8.3.0+10472+7adc332a |
| `mariadb-devel` | Red Hat:enterprise_linux:8::appstream | All versions | 3:10.3.28-1.module+el8.3.0+10472+7adc332a |
| `mariadb-embedded` | Red Hat:enterprise_linux:8::appstream | All versions | 3:10.3.28-1.module+el8.3.0+10472+7adc332a |

Products: Debian Debian Linux, Galeracluster Wsrep, Mariadb Mariadb, Percona Percona Server.

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

Upgrade mariadb to a fixed version for your release line: 10.2.37, 10.3.28, 10.4.18 or 10.5.9.

## Is CVE-2021-27928 being exploited?

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

Public exploit code:

- CVE-2021-27928 MariaDB/MySQL-'wsrep provider' 命令注入漏洞 (github_poc): https://github.com/Al1ex/CVE-2021-27928
- CVE-2021-27928-POC (github_poc): https://github.com/shamo0/CVE-2021-27928-POC
- MariaDB 10.2 - 'wsrep_provider' OS Command Execution (exploitdb)
- A Proof of Concept for the CVE-2021-27928 flaw exploitation (github_poc): https://github.com/LalieA/CVE-2021-27928

## 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-2021-27928 and fix it if it is affected.

What it is: CVE-2021-27928 is a high-severity code injection vulnerability in Debian Debian Linux, published on 19 Mar 2021. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-27928 in the wild and no public exploit code.

Affected packages and fixed versions:
- mariadb (Bitnami): affected from 10.2.0; fixed in 10.2.37, 10.3.28, 10.4.18, 10.5.9
- mariadb-min (Bitnami): affected from 10.2.0; fixed in 10.2.37, 10.3.28, 10.4.18, 10.5.9
- mysql-client (Bitnami): affected from 10.2.0; fixed in 10.2.37, 10.3.28, 10.4.18, 10.5.9

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

## Sources

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

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