{"answers":{"affected":"2 open source packages ship an affected version, including spin-sdk.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-32980 exists.","fix":"Upgrade spin-sdk to 2.4.3 or later.","what":"CVE-2024-32980 is a critical server-side request forgery vulnerability in fermyon spin, published on 8 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-32980 and fix it if it is affected.\n\nWhat it is: CVE-2024-32980 is a critical server-side request forgery vulnerability in fermyon spin, published on 8 May 2024. 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-2024-32980 exists.\n\nAffected packages and fixed versions:\n- spin-sdk (crates.io): affected all versions; fixed in 2.4.3\n- spin-sdk (crates.io): affected all versions; fixed in 2.4.3\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-2024-32980/ (Markdown: https://insights.sbomify.com/CVE-2024-32980/index.md)","id":"CVE-2024-32980","markdown":"https://insights.sbomify.com/CVE-2024-32980/index.md","name":"CVE-2024-32980","record":{"aliases":["GHSA-f3h7-gpjj-wcvh"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Spin serverless runtime","requires_auth":"none","summary":"Attackers can bypass network sandbox restrictions in Spin applications to make requests to arbitrary hosts via manipulated Host headers.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-610","name":"Externally Controlled Reference to a Resource in Another Sphere"}],"description":"Spin is the developer tool for building and running serverless applications powered by WebAssembly. Prior to 2.4.3, some specifically configured Spin applications that use `self` requests without a specified URL authority can be induced to make requests to arbitrary hosts via the `Host` HTTP header. The following conditions need to be met for an application to be vulnerable: 1. The environment Spin is deployed in routes requests to the Spin runtime based on the request URL instead of the `Host` header, and leaves the `Host` header set to its original value; 2. The Spin application's component handling the incoming request is configured with an `allow_outbound_hosts` list containing `\"self\"`; and 3. In reaction to an incoming request, the component makes an outbound request whose URL doesn't include the hostname/port. Spin 2.4.3 has been released to fix this issue.","ecosystems":["crates.io"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Spin contains a potential network sandbox escape for specifically configured Spin applications","id":"CVE-2024-32980","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"ssrf","year":"2024"},"n_packages":2,"n_references":2,"next":{"headline":"Cross-site Scripting vulnerability with encoded payload in silverstripe/framework","id":"CVE-2024-32981"},"packages":[{"ecosystem":"crates.io","fixed":["2.4.3"],"introduced":["0"],"last_affected":[],"package":"spin-sdk","purl":null,"source":"GHSA-f3h7-gpjj-wcvh"},{"ecosystem":"crates.io","fixed":["2.4.3"],"introduced":["0"],"last_affected":[],"package":"spin-sdk","purl":"pkg:cargo/spin-sdk","source":"GHSA-f3h7-gpjj-wcvh"}],"prev":{"headline":"Reflected Cross-site Scripting potential in all object list views in Nautobot","id":"CVE-2024-32979"},"products":["spin"],"published":"2024-05-08","related":[],"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":"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-08-02","vendors":["fermyon"]},"summary":"Attackers can bypass network sandbox restrictions in Spin applications to make requests to arbitrary hosts via manipulated Host headers.","url":"https://insights.sbomify.com/CVE-2024-32980/"}