# CVE-2023-39593: Command injection in n/a

> Authenticated attackers can execute arbitrary commands with elevated privileges via insecure permissions in the sys_exec function.

- **Severity:** Medium 5.6 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Oct 2024
- **Updated:** 20 Oct 2024
- **Also known as:** BIT-mariadb-2023-39593, BIT-mariadb-min-2023-39593, BIT-mysql-client-2023-39593, GHSA-xr59-q2m8-w439, UBUNTU-CVE-2023-39593

## What is CVE-2023-39593?

CVE-2023-39593 is a medium-severity command injection vulnerability in Mariadb Mariadb, published on 17 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Insecure permissions in the sys_exec function of MariaDB v10.5 allows authenticated attackers to execute arbitrary commands with elevated privileges. NOTE: this is disputed by the MariaDB Foundation because no privilege boundary is crossed.

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

## Which versions are affected by CVE-2023-39593?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mariadb` | Bitnami | From 10.5.0 to 10.5.0 | None |
| `mariadb-min` | Bitnami | From 10.5.0 to 10.5.0 | None |
| `mysql-client` | Bitnami | From 10.5.0 to 10.5.0 | None |

Products: Mariadb Mariadb.

## How do I fix CVE-2023-39593?

No fix has been published for CVE-2023-39593 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-39593 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-39593 exists.

Public exploit code:

- Database authenticated code execution (github_poc): https://github.com/Ant1sec-ops/CVE-2023-39593

## Other vulnerabilities in Mariadb Mariadb

- [CVE-2026-49261](https://insights.sbomify.com/CVE-2026-49261/): MariaDB server has unsafe parameter handling in `wsrep_notify_cmd` (critical 10.0)
- [CVE-2026-85746](https://insights.sbomify.com/CVE-2026-85746/): MariaDB: Out-of-bound buffer write on in `ST_AsText` of nested GeometryCollections (critical 9.9)
- [CVE-2026-85748](https://insights.sbomify.com/CVE-2026-85748/): MariaDB: Use-after-free with a large number of SYS_REFCURSOR's (critical 9.9)
- [CVE-2026-92262](https://insights.sbomify.com/CVE-2026-92262/): MariaDB: Numerous issues caused by historical #mysql50# tablename encoding bypass. (critical 9.9)
- [CVE-2023-26785](https://insights.sbomify.com/CVE-2023-26785/): Code injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-39593 and fix it if it is affected.

What it is: CVE-2023-39593 is a medium-severity command injection vulnerability in Mariadb Mariadb, published on 17 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-39593 exists.

Affected packages and fixed versions:
- mariadb (Bitnami): affected from 10.5.0 up to 10.5.0; no fix listed
- mariadb-min (Bitnami): affected from 10.5.0 up to 10.5.0; no fix listed
- mysql-client (Bitnami): affected from 10.5.0 up to 10.5.0; no fix listed

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

## Sources

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

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