<?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>Mon, 05 Oct 2026 20:07:22 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-21653 — vantage6 insecure SSH configuration for node and server containers</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-21653</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; vantage6&lt;/p&gt;
&lt;p&gt;The vantage6 technology enables to manage and deploy privacy enhancing technologies like Federated Learning (FL) and Multi-Party Computation (MPC).  Nodes and servers get a ssh config by default that permits root login with password authentication. In a proper deployment, the SSH service is not exposed so there is no risk, but not all deployments are ideal. The default should therefore be less permissive.  The vulnerability can be mitigated by removing the ssh part from the docker file and rebuilding the docker image.  Version 4.2.0 patches the vulnerability.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; vantage6&lt;/p&gt;
&lt;p&gt;The vantage6 technology enables to manage and deploy privacy enhancing technologies like Federated Learning (FL) and Multi-Party Computation (MPC).  Nodes and servers get a ssh config by default that permits root login with password authentication. In a proper deployment, the SSH service is not exposed so there is no risk, but not all deployments are ideal. The default should therefore be less permissive.  The vulnerability can be mitigated by removing the ssh part from the docker file and rebuilding the docker image.  Version 4.2.0 patches the vulnerability.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-21653</guid>
    </item>
    <item>
      <title>GHSA-2wgc-48g2-cj5w — vantage6 has insecure SSH configuration for node and server containers</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2wgc-48g2-cj5w</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: vantage6&lt;/p&gt;
&lt;p&gt;### Impact
Nodes and servers get a ssh config by default that permits root login with password authentication. In a proper deployment, the SSH service is not exposed so there is no risk, but not all deployments are ideal. The default should therefore be less permissive.&lt;/p&gt;
&lt;p&gt;We will probably opt to completely remove the ssh option as it is only used for debugging. Later, we can add a debug mode where we can activate it if necessary.&lt;/p&gt;
&lt;p&gt;### Workarounds
Remove the ssh part from the docker file and build your own docker image&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: vantage6&lt;/p&gt;
&lt;p&gt;### Impact
Nodes and servers get a ssh config by default that permits root login with password authentication. In a proper deployment, the SSH service is not exposed so there is no risk, but not all deployments are ideal. The default should therefore be less permissive.&lt;/p&gt;
&lt;p&gt;We will probably opt to completely remove the ssh option as it is only used for debugging. Later, we can add a debug mode where we can activate it if necessary.&lt;/p&gt;
&lt;p&gt;### Workarounds
Remove the ssh part from the docker file and build your own docker image&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2wgc-48g2-cj5w</guid>
    </item>
  </channel>
</rss>
