CVE-2023-43652: high-severity vulnerability in jumpserver
Non-MFA account takeover via using only SSH public key to login in jumpserver
Published · Updated
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.2epss 0.8%
exploitation probability
0.8%top 44% of all CVEs
observed exploitation
nono source reports it
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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
Affected products
jumpserver · jumpserverRelated CVEs — jumpserver
In the same product, most dangerous first.
CVE-2023-42442HIGHJumpServer session replays download without authenticationEPSS 63.0%CVE-2023-42820HIGHRandom seed leakage in JumpserverEPSS 6.3%CVE-2024-29201CRITICALJumpServer's insecure Ansible playbook validation leads to RCE in CeleryEPSS 6.0%CVE-2024-29202CRITICALJumpServer vulnerable to Jinja2 template injection in Ansible leads to RCE in CeleryEPSS 5.9%CVE-2023-42819HIGHPath traversal in JumpserverEPSS 2.2%CVE-2023-43651HIGHRemote code execution on the host system via MongoDB shell in jumpserverEPSS 2.1%