{"answers":{"affected":"2 open source packages ship an affected version, including @vrite/sdk. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-5572 exists.","fix":"Upgrade @vrite/sdk to 0.3.0 or later.","what":"CVE-2023-5572 is a critical server-side request forgery vulnerability in vriteio/vrite, published on 13 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-5572 and fix it if it is affected.\n\nWhat it is: CVE-2023-5572 is a critical server-side request forgery vulnerability in vriteio/vrite, published on 13 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-5572 exists.\n\nAffected packages and fixed versions:\n- @vrite/sdk (npm): affected all versions; fixed in 0.3.0\n- @vrite/sdk (npm): affected all versions; fixed in 0.3.0\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-5572/ (Markdown: https://insights.sbomify.com/CVE-2023-5572/index.md)","id":"CVE-2023-5572","markdown":"https://insights.sbomify.com/CVE-2023-5572/index.md","name":"CVE-2023-5572","record":{"aliases":["GHSA-w35p-wxwj-rcm9"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Vrite web application","requires_auth":"none","summary":"An attacker can exploit a Server-Side Request Forgery vulnerability in the Vrite web application to access internal resources or bypass security controls.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntrdev","cpe":[{"product":"vrite","vendor":"vrite"}],"cvss":{"score":10,"severity":"critical","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Server-Side Request Forgery (SSRF) in GitHub repository vriteio/vrite prior to 0.3.0.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Server-Side Request Forgery (SSRF) in vriteio/vrite","id":"CVE-2023-5572","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"ssrf","year":"2023"},"n_packages":2,"n_references":2,"next":{"headline":"Allocation of Resources Without Limits or Throttling in vriteio/vrite","id":"CVE-2023-5573"},"packages":[{"ecosystem":"npm","fixed":["0.3.0"],"introduced":["0"],"last_affected":[],"package":"@vrite/sdk","purl":null,"source":"GHSA-w35p-wxwj-rcm9"},{"ecosystem":"npm","fixed":["0.3.0"],"introduced":["0"],"last_affected":[],"package":"@vrite/sdk","purl":"pkg:npm/%40vrite/sdk","source":"GHSA-w35p-wxwj-rcm9"}],"prev":{"headline":"Improper Input Validation in vriteio/vrite","id":"CVE-2023-5571"},"products":["vriteio/vrite"],"published":"2023-10-13","related":[{"cvss_score":6.5,"headline":"Improper Input Validation in vriteio/vrite","id":"CVE-2023-5571","kev_date_added":null,"published":"2023-10-13"},{"cvss_score":4.7,"headline":"Allocation of Resources Without Limits or Throttling in vriteio/vrite","id":"CVE-2023-5573","kev_date_added":null,"published":"2023-10-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-09-17","vendors":["vriteio"]},"summary":"An attacker can exploit a Server-Side Request Forgery vulnerability in the Vrite web application to access internal resources or bypass security controls.","url":"https://insights.sbomify.com/CVE-2023-5572/"}