CVE-2023-42820
Random seed leakage in Jumpserver
No known exploitation. EPSS puts it in the 94th percentile. Fixed in 2.28.19.
What to do
Find your product and version, then upgrade to the build on the right.
- JumpserverAffected: >= 2.24, < 2.28.19Upgrade to: not statedAffected: >= 3.0.0, < 3.6.5Upgrade to: not statedStated by: CVE record
- Fit2cloud JumpserverAffected: ≥ 2.24.0, < 2.28.19Upgrade to: 2.28.19Stated by: NVD
- Hangzhou Feizhiyun Information Technology Co., Ltd. JumpServerAffected: от 3.0.0 до 3.6.5Upgrade to: not statedStated by: BDU
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
JumpServer is an open source bastion host. This vulnerability is due to exposing the random number seed to the API, potentially allowing the randomly generated verification codes to be replayed, which could lead to password resets. If MFA is enabled users are not affect. Users not using local authentication are also not affected. Users are advised to upgrade to either version 2.28.19 or to 3.6.5. There are no known workarounds or this issue.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
6.3% chance of exploitation activity in the next 30 days, which ranks it in the 94th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
7 events over 1003 days, from the signal feeds we watch.
- OpenVAS check added
- EPSS band changehigh → low
- Patch availablerecord updated
- Publishedweakness classified, att&ck mapped
Affected products
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:L
Scored 7.0 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
- Privileges Required NoneNo authentication required — anyone can exploit this
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality LowSome restricted information is disclosed, but limited in scope
- Integrity HighTotal loss of integrity — attacker can modify any data in the component
- Availability LowReduced performance or intermittent disruption of service
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
Sources
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for JumpServer, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI