{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-0574 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-0574 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-0574 is a medium-severity server-side request forgery vulnerability in YugabyteDB Anywhere, published on 9 Feb 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-0574 and fix it if it is affected.\n\nWhat it is: CVE-2023-0574 is a medium-severity server-side request forgery vulnerability in YugabyteDB Anywhere, published on 9 Feb 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-0574 in the wild and no public exploit code.\n\nAffected product: YugabyteDB Anywhere. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-0574/ (Markdown: https://insights.sbomify.com/CVE-2023-0574/index.md)","id":"CVE-2023-0574","markdown":"https://insights.sbomify.com/CVE-2023-0574/index.md","name":"CVE-2023-0574","record":{"aliases":["GHSA-pvq4-73cw-rg9h"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"YugabyteDB Anywhere","requires_auth":"high_privilege","summary":"Attackers can exploit SSRF and authentication flaws in YugabyteDB Anywhere to access restricted functionality and manipulate communication channels.","user_interaction":"required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Yugabyte","cpe":[{"product":"yugabytedb_managed","vendor":"yugabyte"}],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"},{"id":"CWE-915","name":"Improperly Controlled Modification of Dynamically-Determined Object Attributes"},{"id":"CWE-307","name":"Improper Restriction of Excessive Authentication Attempts"}],"description":"Server-Side Request Forgery (SSRF), Improperly Controlled Modification of Dynamically-Determined Object Attributes, Improper Restriction of Excessive Authentication Attempts vulnerability in YugaByte, Inc. Yugabyte Managed allows Accessing Functionality Not Properly Constrained by ACLs, Communication Channel Manipulation, Authentication Abuse.This issue affects Yugabyte Managed: from 2.0.0.0 through 2.13.0.0","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Server-Side Request Forgery","id":"CVE-2023-0574","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Remote Code Execution","id":"CVE-2023-0575"},"packages":[],"prev":{"headline":"Unchecked Error Condition in froxlor/froxlor","id":"CVE-2023-0572"},"products":["YugabyteDB Anywhere"],"published":"2023-02-09","related":[{"cvss_score":6.7,"headline":"Arbitrary File Write in High Availability Backup Upload","id":"CVE-2023-0745","kev_date_added":null,"published":"2023-02-09"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-24","vendors":["YugabyteDB"]},"summary":"Attackers can exploit SSRF and authentication flaws in YugabyteDB Anywhere to access restricted functionality and manipulate communication channels.","url":"https://insights.sbomify.com/CVE-2023-0574/"}