Account takeover via caller-unverified public-key token issuance
Published Sep 27, 2023 · Updated Mar 25, 2025
Authentication bypass in JumpServer 2.0.0 through 2.28.19 and 3.0.0 through 3.7.0 allows remote attackers to impersonate users. The Core token API accepts a username and matching SSH public key, trusts the caller as KoKo, and issues a personal token without private-key proof. A target account's username and registered public key are required; the token exposes that user's information and authorized actions.
Summary
What happened
Authentication bypass in JumpServer 2.0.0 through 2.28.19 and 3.0.0 through 3.7.0 allows remote attackers to impersonate users. The Core token API accepts a username and matching SSH public key, trusts the caller as KoKo, and issues a personal token without private-key proof. A target account's username and registered public key are required; the token exposes that user's information and authorized actions.
The record
- CVE
- CVE-2023-43652
- Published
- Sep 27, 2023
- Updated
- Mar 25, 2025
- Vendor
- JumpServer
- Product
- JumpServer
- Classifications
- CWE-862, T1078
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 27, 2023CVE publishedPublication date reported by the CVE source.
- Mar 25, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 2.0.0, < 2.28.20
- Affected versionversion=2.0.0 <2.28.20
- Affected versionversion=>= 3.0.0, < 3.7.1
- Affected versionversion=3.0.0 <3.7.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Vendor advisory token-request reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo