dbcve.org
YugabytedbApplication · Yugabyte

CVE-2023-0575

CRITICAL · 9.8 CVSS v3.1 Published 2023-02-09
Fix available
A fix is available. Upgrade to 2.2.0.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Yugabyte DB versions before 2.2.0.0 contain a code injection vulnerability in the DevopsBase.Java (execCommand) and TableManager.Java (runCommand) modules, where user-supplied input via the backup.Py component is not properly sanitized before being passed to system command execution functions. This allows authenticated attackers to inject arbitrary OS commands via API manipulation or privilege abuse, potentially leading to complete system compromise.

MitigationUpgrade Yugabyte DB to version 2.2.0.0 or later. If immediate upgrade is not possible, restrict API access and implement network-level controls to limit exposure to trusted users only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
YugabytedbApplication
Affected:< 2.2.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Yugabyte DB version
    Run 'yb-admin --version' or 'yugabyted --version' from the Yugabyte installation directory, or query the system: SELECT * FROM yb_sys_catalog WHERE key = 'yb_version';
    Affected if The returned version is earlier than 2.2.0.0 (e.g., 2.0.x, 2.1.x, etc.)
  2. Identify backup component exposure
    Check if the backup API endpoints are exposed or accessible. Review network listeners and API access controls for endpoints related to 'backup', 'DevopsBase', or 'TableManager' functionality.
    Affected if Backup-related API endpoints are accessible over the network without proper access restrictions
  3. Verify authenticated API access
    Review user access controls and API authentication settings for the Yugabyte backup functions. Check if untrusted or low-privilege users can access the backup execution APIs.
    Affected if Untrusted or non-admin users have access to the backup command execution APIs
  4. Confirm Java module presence
    Inspect the Yugabyte installation for the presence of DevopsBase.Java and TableManager.Java class files in the Java classpath or lib directories, typically under the server or admin tool directories.
    Affected if These modules exist in the installation and the backup feature is enabled

You are affected if your Yugabyte DB version is below 2.2.0.0 AND the backup API or related command execution features are accessible to users who should not have OS command injection capability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.2.0.0 or later
Fixed in 2.2.0.0
Interim mitigation

Upgrade Yugabyte DB to version 2.2.0.0 or later. If immediate upgrade is not possible, restrict API access and implement network-level controls to limit exposure to trusted users only.

Recommended fix High confidence

2.2.0.0 or later

  1. Review the YugabyteDB upgrade documentation at docs.yugabyte.com for your deployment type
  2. Ensure you have a complete backup of your database data and configuration
  3. Stop all YugabyteDB services in your cluster
  4. Upgrade YugabyteDB to version 2.2.0.0 or later following the appropriate upgrade procedure for your deployment (rolling upgrade or full cluster restart)
  5. After upgrade, verify all services are running correctly
  6. Validate that the backup.Py functionality and related modules (DevopsBase.Java:execCommand, TableManager.Java:runCommand) are functioning properly
Caveat Review upgrade documentation for any configuration changes required between your current version and 2.2.0.0; test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Yugabytedb Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-0575 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-0575 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data