<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 08 Oct 2026 09:37:08 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-32980 — Spin contains a potential network sandbox escape for specifically configured Spin applications</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-32980</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; fermyon spin&lt;/p&gt;
&lt;p&gt;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&amp;#39;s component handling the incoming request is configured with an `allow_outbound_hosts` list containing `&amp;#34;self&amp;#34;`; and 3. In reaction to an incoming request, the component makes an outbound request whose URL doesn&amp;#39;t include the hostname/port. Spin 2.4.3 has been released to fix this issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; fermyon spin&lt;/p&gt;
&lt;p&gt;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&amp;#39;s component handling the incoming request is configured with an `allow_outbound_hosts` list containing `&amp;#34;self&amp;#34;`; and 3. In reaction to an incoming request, the component makes an outbound request whose URL doesn&amp;#39;t include the hostname/port. Spin 2.4.3 has been released to fix this issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-32980</guid>
    </item>
  </channel>
</rss>
