First published: Wed Sep 27 2023(Updated: )
JumpServer is an open source bastion host. As an unauthenticated user, it is possible to authenticate to the core API with a username and an SSH public key without needing a password or the corresponding SSH private key. An SSH public key should be considered public knowledge and should not used as an authentication secret alone. JumpServer provides an API for the KoKo component to validate user private key logins. This API does not verify the source of requests and will generate a personal authentication token. Given that public keys can be easily leaked, an attacker can exploit the leaked public key and username to authenticate, subsequently gaining access to the current user's information and authorized actions. This issue has been addressed in versions 2.28.20 and 3.7.1. Users are advised to upgrade. There are no known workarounds for this vulnerability.
Credit: security-advisories@github.com security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Fit2cloud Jumpserver | >=2.0.0<2.28.20 | |
Fit2cloud Jumpserver | >=3.0.0<3.7.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2023-43652 is a vulnerability in the Fit2cloud Jumpserver software that allows unauthenticated users to authenticate to the core API without needing a password or SSH private key.
CVE-2023-43652 affects Fit2cloud Jumpserver versions 2.0.0 to 2.28.20 and versions 3.0.0 to 3.7.1, allowing unauthenticated users to bypass authentication.
The severity of CVE-2023-43652 is classified as critical with a CVSS score of 9.1.
To mitigate the vulnerability, it is recommended to update Fit2cloud Jumpserver to a version higher than 2.28.20 or 3.7.1.
You can find more information about CVE-2023-43652 at the following URL: https://github.com/jumpserver/jumpserver/security/advisories/GHSA-fr8h-xh5x-r8g9