Cyber Resilience

CVE-2023-46138

Auth Bypass in Fit2Cloud Jumpserver ≤ 3.8.0

Published
31 October 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 3.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS Score 0.0032 24th percentile
Risk Priority 32 floored blend · peak EPSS

Summary

CVE-2023-46138 is a low-severity Weak Password Recovery Mechanism for Forgotten Password (CWE-640) vulnerability in Fit2Cloud Jumpserver. Its CVSS base score is 3.7 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Valid Accounts (T1078); ranked at the 24th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

JumpServer is an open source bastion host and maintenance security audit system that complies with 4A specifications. Prior to version 3.8.0, the default email for initial user admin is `admin[@]mycompany[.]com`, and users reset their passwords by sending an email. Currently,…

more

the domain `mycompany.com` has not been registered. However, if it is registered in the future, it may affect the password reset functionality. This issue has been patched in version 3.8.0 by changing the default email domain to `example.com`. Those who cannot upgrade may change the default email domain to `example.com` manually.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1078 Valid Accounts Stealth
Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.
T1110 Brute Force Credential Access
Adversaries may use brute force techniques to gain access to accounts when passwords are unknown or when password hashes are obtained.
T1110.001 Password Guessing Credential Access
Adversaries with no prior knowledge of legitimate credentials within the system or environment may guess passwords to attempt access to accounts.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-43650Same product: Fit2Cloud Jumpserver
CVE-2023-46123Same product: Fit2Cloud Jumpserver
CVE-2025-27095Same product: Fit2Cloud Jumpserver
CVE-2023-42818Same product: Fit2Cloud Jumpserver
CVE-2023-43651Same product: Fit2Cloud Jumpserver
CVE-2023-42820Same product: Fit2Cloud Jumpserver
CVE-2026-31864Same product: Fit2Cloud Jumpserver
CVE-2023-43652Same product: Fit2Cloud Jumpserver
CVE-2024-29201Same product: Fit2Cloud Jumpserver
CVE-2023-42819Same product: Fit2Cloud Jumpserver

Affected Assets

fit2cloud
jumpserver
≤ 3.8.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V7.4.3

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-640

Establishing procedures for lost or compromised authenticators addresses weak password recovery mechanisms.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-01 mostly match
prevents

Credential lifecycle management directly includes password reset/recovery flows.

PR.AA-02 mostly match
prevents

Identity proofing is the core control that prevents weak or bypassed recovery mechanisms.

PR.AA-03 partial match
prevents

Authentication policy covers strength/MFA but does not address recovery path weaknesses.

PR.PS-06 partial match
prevents

Secure SDLC reduces implementation flaws but is not specific to password-recovery design.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

degrades

Strong authentication-information lifecycle rules directly address weak password-recovery flows.

prevents

Secure-SDLC practices can embed strong recovery design, yet the control is broader than this single weakness.

prevents

Application-security requirements can mandate secure recovery flows, but the control covers many other requirements.

prevents

Secure-coding standards can prevent weak recovery implementations, yet the control is wider in scope.

mitigates

Secure-authentication requirements include robust forgotten-password procedures.

none

Proper access-rights provisioning can limit who can trigger recovery, but does not fix the recovery mechanism itself.

References