{"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-5573 exists.","fix":"Upgrade @vrite/sdk to 0.3.0 or later.","what":"CVE-2023-5573 is a medium-severity denial of service vulnerability in vriteio/vrite, published on 13 Oct 2023. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-5573 and fix it if it is affected.\n\nWhat it is: CVE-2023-5573 is a medium-severity denial of service vulnerability in vriteio/vrite, published on 13 Oct 2023. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-5573 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-5573/ (Markdown: https://insights.sbomify.com/CVE-2023-5573/index.md)","id":"CVE-2023-5573","markdown":"https://insights.sbomify.com/CVE-2023-5573/index.md","name":"CVE-2023-5573","record":{"aliases":["GHSA-5ghm-h2wq-g3mh"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"npm library","requires_auth":"high_privilege","summary":"Attackers can cause denial of service by exploiting resource allocation limits in the vrite library.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntrdev","cpe":[{"product":"vrite","vendor":"vrite"}],"cvss":{"score":4.7,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L","version":"3.0"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"Allocation of Resources Without Limits or Throttling 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":"Allocation of Resources Without Limits or Throttling in vriteio/vrite","id":"CVE-2023-5573","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2023"},"n_packages":2,"n_references":2,"next":{"headline":"Xorg-x11-server: use-after-free bug in damagedestroy","id":"CVE-2023-5574"},"packages":[{"ecosystem":"npm","fixed":["0.3.0"],"introduced":["0"],"last_affected":[],"package":"@vrite/sdk","purl":null,"source":"GHSA-5ghm-h2wq-g3mh"},{"ecosystem":"npm","fixed":["0.3.0"],"introduced":["0"],"last_affected":[],"package":"@vrite/sdk","purl":"pkg:npm/%40vrite/sdk","source":"GHSA-5ghm-h2wq-g3mh"}],"prev":{"headline":"Server-Side Request Forgery (SSRF) in vriteio/vrite","id":"CVE-2023-5572"},"products":["vriteio/vrite"],"published":"2023-10-13","related":[{"cvss_score":10,"headline":"Server-Side Request Forgery (SSRF) in vriteio/vrite","id":"CVE-2023-5572","kev_date_added":null,"published":"2023-10-13"},{"cvss_score":6.5,"headline":"Improper Input Validation in vriteio/vrite","id":"CVE-2023-5571","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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-09-17","vendors":["vriteio"]},"summary":"Attackers can cause denial of service by exploiting resource allocation limits in the vrite library.","url":"https://insights.sbomify.com/CVE-2023-5573/"}