Security readout for executives and security teams
Plain-English summary
CVE-2023-0574 is a medium-severity Yugabyte Managed issue involving SSRF, unsafe dynamic attribute modification, and weak protection against repeated authentication attempts. The CVSS vector indicates exploitation requires network access, high privileges, and user interaction, but successful abuse could significantly affect confidentiality, integrity, and availability.
Executive priority
Treat this as a moderate-priority exposure review for Yugabyte environments. It is not presented as actively exploited, but affected management-plane systems could face serious impact if a privileged attacker abuses it.
Technical view
The CVE maps to CWE-918, CWE-915, and CWE-307. Public data says Yugabyte Managed versions 2.0.0.0 through 2.13.0.0 are affected. The affected-product metadata is inconsistent, naming YugabyteDB Anywhere with defaultStatus unaffected, so product scoping should be verified against vendor records.
Likely exposure
Exposure is most likely in environments using Yugabyte Managed versions 2.0.0.0 through 2.13.0.0. The source bundle does not establish whether cloud-hosted, self-managed, or YugabyteDB Anywhere deployments are equivalently affected.
Exploitation context
The CVE is not listed as CISA KEV in the provided bundle, and no cited source states active exploitation. The CVSS vector suggests abuse is constrained by high required privileges and user interaction, despite high potential impact after exploitation.
Researcher notes
The public bundle is sparse and internally inconsistent on affected product naming. Avoid assuming exploitability beyond the CVSS vector and stated CWEs. Validation should focus on version scope, privilege boundaries, outbound request behavior, and vendor-confirmed remediation.
Mitigation direction
- Check Yugabyte guidance for affected version and product naming clarification.
- Upgrade or remediate according to Yugabyte’s official advisory when identified.
- Restrict network access to Yugabyte management interfaces and APIs.
- Review privileged user access and remove unnecessary administrative permissions.
- Monitor authentication abuse and unusual outbound management-plane requests.
Validation and detection
- Inventory Yugabyte Managed deployments and record exact versions.
- Confirm whether any deployment is between 2.0.0.0 and 2.13.0.0.
- Verify exposed management endpoints are restricted to trusted networks.
- Review logs for suspicious authenticated activity and repeated authentication attempts.
- Check vendor documentation for patch, upgrade, or compensating-control instructions.
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-307: 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-915: 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-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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 lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2023-0574 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
- Medium
- CVSS
- 6.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/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:R/S:U/C:H/I:H/A:H0.95.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.8MediumVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/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.
Improper Restriction of Excessive Authentication Attempts
Improper Restriction of Excessive Authentication Attempts represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improperly Controlled Modification of Dynamically-Determined Object Attributes
Improperly Controlled Modification of Dynamically-Determined Object Attributes represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.