{"answers":{"affected":"2 open source packages ship an affected version, including nuxt-api-party. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-49799 exists.","fix":"Upgrade nuxt-api-party to 0.22.0 or later.","what":"CVE-2023-49799 is a high-severity server-side request forgery vulnerability in johannschopplich nuxt-api-party, published on 8 Dec 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-49799 and fix it if it is affected.\n\nWhat it is: CVE-2023-49799 is a high-severity server-side request forgery vulnerability in johannschopplich nuxt-api-party, published on 8 Dec 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-49799 exists.\n\nAffected packages and fixed versions:\n- nuxt-api-party (npm): affected all versions; fixed in 0.22.0\n- nuxt-api-party (npm): affected all versions; fixed in 0.22.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-49799/ (Markdown: https://insights.sbomify.com/CVE-2023-49799/index.md)","id":"CVE-2023-49799","markdown":"https://insights.sbomify.com/CVE-2023-49799/index.md","name":"CVE-2023-49799","record":{"aliases":["GHSA-3wfp-253j-5jxv"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Nuxt API proxy module","requires_auth":"none","summary":"Attackers can bypass URL validation using whitespace to perform Server-Side Request Forgery, potentially leaking credentials or accessing internal services.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"nuxt_api_party","vendor":"johannschopplich"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"`nuxt-api-party` is an open source module to proxy API requests. nuxt-api-party attempts to check if the user has passed an absolute URL to prevent the aforementioned attack. This has been recently changed to use the regular expression `^https?://`, however this regular expression can be bypassed by an absolute URL with leading whitespace. For example `\\nhttps://whatever.com` which has a leading newline. According to the fetch specification, before a fetch is made the URL is normalized. \"To normalize a byte sequence potentialValue, remove any leading and trailing HTTP whitespace bytes from potentialValue.\". This means the final request will be normalized to `https://whatever.com` bypassing the check and nuxt-api-party will send a request outside of the whitelist. This could allow us to leak credentials or perform Server-Side Request Forgery (SSRF). This vulnerability has been addressed in version 0.22.1. Users are advised to upgrade. Users unable to upgrade should revert to the previous method of detecting absolute URLs.","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 in nuxt-api-party","id":"CVE-2023-49799","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"ssrf","year":"2023"},"n_packages":2,"n_references":5,"next":{"headline":"Denial of service by abusing `fetchOptions.retry` in nuxt-api-party","id":"CVE-2023-49800"},"packages":[{"ecosystem":"npm","fixed":["0.22.0"],"introduced":["0"],"last_affected":[],"package":"nuxt-api-party","purl":null,"source":"GHSA-3wfp-253j-5jxv"},{"ecosystem":"npm","fixed":["0.22.0"],"introduced":["0"],"last_affected":[],"package":"nuxt-api-party","purl":"pkg:npm/nuxt-api-party","source":"GHSA-3wfp-253j-5jxv"}],"prev":{"headline":"Duplicated execution of subcalls in OpenZeppelin Contracts","id":"CVE-2023-49798"},"products":["nuxt-api-party"],"published":"2023-12-08","related":[{"cvss_score":7.5,"headline":"Denial of service by abusing `fetchOptions.retry` in nuxt-api-party","id":"CVE-2023-49800","kev_date_added":null,"published":"2023-12-08"}],"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":"partial"},"state":"PUBLISHED","updated":"2024-11-27","vendors":["johannschopplich"]},"summary":"Attackers can bypass URL validation using whitespace to perform Server-Side Request Forgery, potentially leaking credentials or accessing internal services.","url":"https://insights.sbomify.com/CVE-2023-49799/"}