Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

crates.io package

spin-sdk

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Critical, CVSS 9.1crates.ioPublished

    Spin applications with specific configuration vulnerable to potential network sandbox escape

    CVE-2024-32980 · GHSA-f3h7-gpjj-wcvh

    Affected
    • crates.io spin-sdk < 2.4.3
    Fixed in
    2.4.3· Vendor fix available
    Issue
    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 and code such as 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 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: 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 the original value by the client. 2. The Spin application's component handling the incoming request is configured…

    Recommended action: Upgrade to 2.4.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →