Search for packages
| purl | pkg:pypi/vantage6-node@3.8.8 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-27hu-bwc5-43ca
Aliases: CVE-2024-21653 GHSA-2wgc-48g2-cj5w PYSEC-2024-33 PYSEC-2024-34 |
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. |
Affected by 0 other vulnerabilities. |
|
VCID-g2kx-nbgv-jffy
Aliases: CVE-2023-47631 GHSA-vc3v-ppc7-v486 PYSEC-2023-303 PYSEC-2023-304 |
vantage6 is a framework to manage and deploy privacy enhancing technologies like Federated Learning (FL) and Multi-Party Computation (MPC). In affected versions a node does not check if an image is allowed to run if a `parent_id` is set. A malicious party that breaches the server may modify it to set a fake `parent_id` and send a task of a non-whitelisted algorithm. The node will then execute it because the `parent_id` that is set prevents checks from being run. This impacts all servers that are breached by an expert user. This vulnerability has been patched in version 4.1.2. All users are advised to upgrade. There are no known workarounds for this vulnerability. |
Affected by 1 other vulnerability. |
|
VCID-pnkd-5grr-hfgs
Aliases: CVE-2023-28635 GHSA-7x94-6g2m-3hp2 PYSEC-2023-198 |
vantage6 is privacy preserving federated learning infrastructure. Prior to version 4.0.0, malicious users may try to get access to resources they are not allowed to see, by creating resources with integers as names. One example where this is a risk, is when users define which users are allowed to run algorithms on their node. This may be defined by username or user id. Now, for example, if user id 13 is allowed to run tasks, and an attacker creates a username with username '13', they would be wrongly allowed to run an algorithm. There may also be other places in the code where such a mixup of resource ID or name leads to issues. Version 4.0.0 contains a patch for this issue. The best solution is to check when resources are created or modified, that the resource name always starts with a character. |
Affected by 0 other vulnerabilities. Affected by 2 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| This package is not known to fix vulnerabilities. | ||