CVE-2023-42818: medium-severity vulnerability in jumpserver
SSH public key login without private key challenge if mfa is enabled in jumpserver
Published · Updated
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 5.4epss 0.7%
exploitation probability
0.7%top 49% of all CVEs
observed exploitation
nono source reports it
JumpServer is an open source bastion host. When users enable MFA and use a public key for authentication, the Koko SSH server does not verify the corresponding SSH private key. An attacker could exploit a vulnerability by utilizing a disclosed public key to attempt brute-force authentication against the SSH service This issue has been patched in versions 3.6.5 and 3.5.6. Users are advised to upgrade. There are no known workarounds for this issue.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
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%