CVE-2024-21653: vantage6 insecure SSH configuration for node and server containers

Published Jan 30, 2024
·
Updated

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.

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.

Workarounds Remove the ssh part from the docker file and build your own docker image

Other sources

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.

MITRE

Affected Software

2 affected componentsFixes available
pip/vantage6<4.2.0
4.2.0
Vantage6 Vantage6<4.2.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pip/vantage6 to a version that resolves this vulnerability.

    Fixed in 4.2.0
  2. Upgrade

    Upgrade vantage6 to a version that resolves this vulnerability.

    Fixed in 4.2.0
  3. Remove

    Remove SSH option in node and server containers from your environment.

    Remove the SSH part from the Dockerfile and rebuild your own Docker image to mitigate the insecure SSH configuration (root login with password authentication by default).

Event History

Jan 30, 2024
CVE Published
via MITRE·03:39 PM
Data Sourced
via MITRE·03:39 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·08:56 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-21653?

CVE-2024-21653 is considered a moderate severity vulnerability due to the risk of unauthorized root access.

2

How do I fix CVE-2024-21653?

To fix CVE-2024-21653, configure the SSH service to disable root login and use key-based authentication instead.

3

Which versions are affected by CVE-2024-21653?

CVE-2024-21653 affects Vantage6 versions prior to 4.2.0.

4

Who is impacted by CVE-2024-21653?

Users and administrators of Vantage6 who have not secured their SSH configurations are impacted by CVE-2024-21653.

5

What are the potential risks of CVE-2024-21653?

The potential risks of CVE-2024-21653 include unauthorized access and exploitation of systems due to permissive SSH configurations.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203