Summary
Spin applications with specific configuration vulnerable to potential network sandbox escape
Vulnerable Configurations
The following conditions need to be met for an application to be vulnerable:
- The environment Spin is deployed in routes requests to the Spin runtime based on the request URL instead of the
Hostheader, and leaves theHostheader set to the original value by the client. - The Spin application's component handling the incoming request is configured with an
allowed_outbound_hostslist containing"self". - In reaction to an incoming request, the component makes an outbound request whose URL doesn't include the hostname/port.
If all of these conditions apply, then Spin will use the inbound request's Host header to determine the authority part of the URL if none is explicitly provided in the request's URL.
Setups known not to be vulnerable
Fermyon's Fermyon Cloud serverless product and applications hosted on it are known not to be vulnerable.
Workarounds
For deployments of Spin, a workaround is to ensure that the Host header is sanitized to match the application a request is routed to.
For individual applications, multiple workarounds exist:
- Ensure that outgoing requests always sanitize the
Hostheader - Ensure that outgoing requests always provide the hostname in the URL and use that hostname in the
allowed_outbound_hostslist instead ofself - When using Spin 2.4, use application-internal service chaining for intra-application requests
Impact
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.
If an application's manifest contains a component with configuration such as
allowed_outbound_hosts = ["http://self", "https://self"]
and code such as
let res: Response = spin_sdk::http::send(
Request::new(Method::Get, "/") // Note: the request URI does not contain a URL authority
).await?;
Then that application can be induced to send an outgoing request to another host (leading the app to process the response assuming it comes from another component in the same application). This can be induced with a request such as
curl -H"Host: google.com:80" localhost:3000 # Assuming the application is served on localhost:3000
Note: If using a SDK that does not use wasi:http/outgoing-handler, the port can be omitted from the URL.
CVE-2024-32980 has a CVSS score of 9.1 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.4.3); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Has the problem been patched? What versions should users upgrade to?
Spin version 2.4.3 is being released with this advisory going public.
Frequently Asked Questions
- What is CVE-2024-32980? CVE-2024-32980 is a critical-severity security vulnerability in spin-sdk (rust), affecting versions < 2.4.3. It is fixed in 2.4.3.
- How severe is CVE-2024-32980? CVE-2024-32980 has a CVSS score of 9.1 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of spin-sdk are affected by CVE-2024-32980? spin-sdk (rust) versions < 2.4.3 is affected.
- Is there a fix for CVE-2024-32980? Yes. CVE-2024-32980 is fixed in 2.4.3. Upgrade to this version or later.
- Is CVE-2024-32980 exploitable, and should I be worried? Whether CVE-2024-32980 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2024-32980 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2024-32980? Upgrade
spin-sdkto 2.4.3 or later.