# CVE-2023-43650: Non-MFA account takeover via brute-force attack on weak password reset code in jumpserver

> Attackers can take over accounts by brute-forcing weak password reset codes due to missing rate limiting in JumpServer.

- **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-mwx4-8fwc-2xvw

## What is CVE-2023-43650?

CVE-2023-43650 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. The verification code for resetting user's password is vulnerable to brute-force attacks due to the absence of rate limiting. JumpServer provides a feature allowing users to reset forgotten passwords. Affected users are sent a 6-digit verification code, ranging from 000000 to 999999, to facilitate the password reset. Although the code is only available in 1 minute, this window potentially allows for up to 1,000,000 validation attempts. 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-640 (Weak Password Recovery Mechanism for Forgotten Password)

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

It affects 1 product.


Products: Fit2cloud Jumpserver.

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

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

## Is CVE-2023-43650 being exploited?

There is no known exploitation of CVE-2023-43650 in the wild and no public exploit code.

## 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-43650 and fix it if it is affected.

What it is: CVE-2023-43650 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: There is no known exploitation of CVE-2023-43650 in the wild and no public exploit code.

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-43650/ (Markdown: https://insights.sbomify.com/CVE-2023-43650/index.md)
```

## Sources

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

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