CVE-2024-32980 is a critical-severity (CVSS 9.1) CWE-610 vulnerability in spin-sdk. A fix is available for spin-sdk — see the affected versions and patch details below.
Spin contains a potential network sandbox escape for specifically configured Spin applications
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-32980.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2024-32980 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
spin-sdkReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.
Description
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.
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.
Patches
Has the problem been patched? What versions should users upgrade to? Spin version 2.4.3 is being released with this advisory going public.
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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | spin-sdk | all versions | 2.4.3cargo update -p spin-sdk --precise 2.4.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for spin-sdk, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update spin-sdk to 2.4.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-32980 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-32980 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2024-32980. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2024-32980 in your dependencies?
O3 Security finds CVE-2024-32980 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.