SSH public key login without private key challenge if mfa is enabled in jumpserver
jumpserver
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/jumpserver/koko Go |
| No fix yet |
| github.com/jumpserver/jumpserver Go |
|
|
jumpserver
| Product | Affected | Fixed in |
|---|---|---|
| github.com/jumpserver/koko Go |
| No fix yet |
| github.com/jumpserver/jumpserver Go |
|
|
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.
From the CVE record · GitHub_M
When MFA and public-key authentication are enabled, the Koko SSH server does not verify the corresponding SSH private key. An attacker with a disclosed public key can attempt brute-force authentication against the SSH service. The input does not specify whether other credentials or user interaction are required.
Operators of JumpServer using github.com/jumpserver/jumpserver versions below 3.5.6+incompatible or from 3.6.0+incompatible to below 3.6.5+incompatible, and users of any version of github.com/jumpserver/koko, should check their deployments.