Security readout for executives and security teams
Plain-English summary
CVE-2023-0575 is a high-severity remote code execution issue in YugabyteDB versions earlier than 2.2.0.0. The CVE indicates a highly privileged attacker could manipulate API-controlled state or code generation paths to impact confidentiality, integrity, and availability.
Executive priority
Treat this as a high-priority exposure review for legacy YugabyteDB. The business risk is serious if affected deployments exist, but urgency is moderated by the high-privilege requirement and lack of cited active exploitation evidence.
Technical view
The record maps to CWE-642 and CWE-94 in YugabyteDB, citing DevopsBase.Java:execCommand, TableManager.Java:runCommand, and backup.Py. CVSS 3.1 is 7.2: network reachable, low complexity, high privileges required, no user interaction, unchanged scope, and high CIA impact.
Likely exposure
Exposure is likely limited to environments running YugabyteDB 2.0 or other versions earlier than 2.2.0.0, especially where privileged API or operational access is broadly granted to users, services, or automation.
Exploitation context
The source bundle does not show CISA KEV listing or other evidence of active exploitation. The CVSS vector indicates exploitation requires high privileges but no user interaction and can be attempted over a network path.
Researcher notes
Evidence is sparse: the bundle provides CVE metadata, affected version bounds, weakness classes, modules, and CVSS, but no detailed vendor advisory, patch note, or exploit narrative. Avoid assuming broader affected products or exploitation beyond the supplied record.
Mitigation direction
- Inventory YugabyteDB deployments and identify versions earlier than 2.2.0.0.
- Plan upgrade away from affected versions, following YugabyteDB guidance.
- Restrict privileged API, admin, backup, and DevOps access to trusted operators only.
- Review service-account privileges used by YugabyteDB automation.
- Monitor vendor advisories for specific fixed builds or compensating controls.
Validation and detection
- Confirm YugabyteDB version for every cluster and host.
- Identify any deployments running 2.0 or earlier than 2.2.0.0.
- Review who can access privileged YugabyteDB APIs and operational tooling.
- Check logs for unusual privileged API manipulation or command execution activity.
- Verify backup and DevOps automation accounts use least privilege.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-642: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2023-0575 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H1.25.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.2HighVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.yugabyte.com/CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
External Control of Critical State Data
External Control of Critical State Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.