# CVE-2023-43652: Non-MFA account takeover via using only SSH public key to login in jumpserver

> Attackers can authenticate using only a leaked SSH public key and username, bypassing MFA and gaining unauthorized access to user accounts.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Sep 2023
- **Updated:** 25 Mar 2025
- **Also known as:** GHSA-fr8h-xh5x-r8g9

## What is CVE-2023-43652?

CVE-2023-43652 is a high-severity authentication bypass vulnerability in jumpserver, published on 27 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2023-43652?

It affects 1 product.


Products: Fit2cloud Jumpserver.

## How do I fix CVE-2023-43652?

No fix has been published for CVE-2023-43652 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-43652 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-43652 exists.

## Other vulnerabilities in jumpserver

- [CVE-2024-40628](https://insights.sbomify.com/CVE-2024-40628/): Arbitrary File Read in Ansible Playbooks in Jumpserver (critical 10.0)
- [CVE-2024-40629](https://insights.sbomify.com/CVE-2024-40629/): Arbitrary File Write in Ansible Playbooks leads to RCE in Jumpserver (critical 10.0)
- [CVE-2024-29201](https://insights.sbomify.com/CVE-2024-29201/): JumpServer's insecure Ansible playbook validation leads to RCE in Celery (critical 10.0)
- [CVE-2024-29202](https://insights.sbomify.com/CVE-2024-29202/): JumpServer vulnerable to Jinja2 template injection in Ansible leads to RCE in Celery (critical 10.0)
- [CVE-2023-48193](https://insights.sbomify.com/CVE-2023-48193/): Security feature bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-43652 and fix it if it is affected.

What it is: CVE-2023-43652 is a high-severity authentication bypass vulnerability in jumpserver, published on 27 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-43652 exists.

Affected product: jumpserver. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-43652/ (Markdown: https://insights.sbomify.com/CVE-2023-43652/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-43652
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-43652
- OSV: https://osv.dev/vulnerability/CVE-2023-43652

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-43652/
Summaries are generated and may contain mistakes; the official description above is the record.