# CVE-2023-0575: Remote Code Execution


- **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
- **Fix available:** No
- **Published:** 9 Feb 2023
- **Updated:** 24 Mar 2025
- **Also known as:** GHSA-38h3-jcwf-hx88

## What is CVE-2023-0575?

CVE-2023-0575 is a high-severity vulnerability in YugabyteDB, published on 9 Feb 2023. 

### Official description

External Control of Critical State Data, Improper Control of Generation of Code ('Code Injection') vulnerability in YugaByte, Inc. Yugabyte DB on Windows, Linux, MacOS, iOS (DevopsBase.Java:execCommand, TableManager.Java:runCommand modules) allows API Manipulation, Privilege Abuse. This vulnerability is associated with program files backup.Py.

This issue affects Yugabyte DB: Lesser then 2.2.0.0

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-642 (External Control of Critical State Data)

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

It affects 1 product.


Products: Yugabyte Yugabytedb.

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

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

## Is CVE-2023-0575 being exploited?

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

## Other vulnerabilities in YugabyteDB

- [CVE-2022-37397](https://insights.sbomify.com/CVE-2022-37397/): The software is vulnerable when using LDAP-based authentication in YCQL with Microsoft’s Active Directory (high 8.3)
- [CVE-2024-41435](https://insights.sbomify.com/CVE-2024-41435/): Memory corruption in n/a (high 7.5)
- [CVE-2023-6002](https://insights.sbomify.com/CVE-2023-6002/): Log Injection (medium 6.5)
- [CVE-2023-4640](https://insights.sbomify.com/CVE-2023-4640/): Set Logging Level Without Authentication (medium 6.5)
- [CVE-2023-6001](https://insights.sbomify.com/CVE-2023-6001/): Prometheus Metrics Accessible Pre-Authentication (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-0575 is a high-severity vulnerability in YugabyteDB, published on 9 Feb 2023. 
Exploitation: There is no known exploitation of CVE-2023-0575 in the wild and no public exploit code.

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

## Sources

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

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