{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-43650 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-43650 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2023-43650 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2023-43650 in the wild and no public exploit code.\n\nAffected product: jumpserver. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-43650/ (Markdown: https://insights.sbomify.com/CVE-2023-43650/index.md)","id":"CVE-2023-43650","markdown":"https://insights.sbomify.com/CVE-2023-43650/index.md","name":"CVE-2023-43650","record":{"aliases":["GHSA-mwx4-8fwc-2xvw"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"JumpServer bastion host","requires_auth":"none","summary":"Attackers can take over accounts by brute-forcing weak password reset codes due to missing rate limiting in JumpServer.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"jumpserver","vendor":"fit2cloud"}],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-640","name":"Weak Password Recovery Mechanism for Forgotten Password"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Non-MFA account takeover via brute-force attack on weak password reset code in jumpserver","id":"CVE-2023-43650","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Remote code execution on the host system via MongoDB shell in jumpserver","id":"CVE-2023-43651"},"packages":[],"prev":{"headline":"baserCMS CSRF vulnerability in Content preview Feature","id":"CVE-2023-43649"},"products":["jumpserver"],"published":"2023-09-27","related":[{"cvss_score":10,"headline":"Arbitrary File Read in Ansible Playbooks in Jumpserver","id":"CVE-2024-40628","kev_date_added":null,"published":"2024-07-18"},{"cvss_score":10,"headline":"Arbitrary File Write in Ansible Playbooks leads to RCE in Jumpserver","id":"CVE-2024-40629","kev_date_added":null,"published":"2024-07-18"},{"cvss_score":10,"headline":"JumpServer's insecure Ansible playbook validation leads to RCE in Celery","id":"CVE-2024-29201","kev_date_added":null,"published":"2024-03-29"},{"cvss_score":10,"headline":"JumpServer vulnerable to Jinja2 template injection in Ansible leads to RCE in Celery","id":"CVE-2024-29202","kev_date_added":null,"published":"2024-03-29"},{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2023-48193","kev_date_added":null,"published":"2023-11-28"},{"cvss_score":9.6,"headline":"JumpServer Connection Token Leak Vulnerability","id":"CVE-2025-62712","kev_date_added":null,"published":"2025-10-30"},{"cvss_score":8.9,"headline":"Path traversal in Jumpserver","id":"CVE-2023-42819","kev_date_added":null,"published":"2023-09-26"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-25","vendors":["jumpserver"]},"summary":"Attackers can take over accounts by brute-forcing weak password reset codes due to missing rate limiting in JumpServer.","url":"https://insights.sbomify.com/CVE-2023-43650/"}