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.
Metrics
Affected Vendors & Products
References
History
Mon, 23 Sep 2024 19:30:00 +0000
Type | Values Removed | Values Added |
---|---|---|
First Time appeared |
Jumpserver
Jumpserver jumpserver |
|
CPEs | cpe:2.3:a:jumpserver:jumpserver:*:*:*:*:*:*:*:* | |
Vendors & Products |
Jumpserver
Jumpserver jumpserver |
|
Metrics |
ssvc
|
MITRE
Status: PUBLISHED
Assigner: GitHub_M
Published: 2023-09-27T18:31:41.320Z
Updated: 2024-09-23T19:07:28.412Z
Reserved: 2023-09-20T15:35:38.147Z
Link: CVE-2023-43652
Vulnrichment
Updated: 2024-08-02T19:44:43.828Z
NVD
Status : Modified
Published: 2023-09-27T19:15:12.133
Modified: 2024-11-21T08:24:33.017
Link: CVE-2023-43652
Redhat
No data.