dbcve.org
JumpserverApplication

CVE-2021-3169

CRITICAL · 9.8 CVSS v3.1 Published 2021-07-23
Fix available
A fix is available. Upgrade to 2.4.5 / 2.5.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An issue in Jumpserver before 2.6.2, before 2.5.4, before 2.4.5 allows attackers to create a connection token through an API which does not have access control and use it to access sensitive assets.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Jumpserver versions before 2.6.2, 2.5.4, and 2.4.5 contain an API endpoint for creating connection tokens that lacks proper access control enforcement. Attackers can directly invoke this unauthenticated or unauthorized API to generate valid connection tokens and use them to access sensitive assets within the infrastructure.

MitigationUpgrade Jumpserver to version 2.6.2, 2.5.4, 2.4.5 or later to obtain the security patch. Additionally, audit API endpoints for access control gaps and implement proper authentication/authorization checks on all token creation mechanisms.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JumpserverApplication
Affected:>= 2.4.0, < 2.4.5>= 2.5.0, < 2.5.4>= 2.6.0, < 2.6.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Jumpserver installation version
    Check the version file or use the Jumpserver command line interface. Common locations include the /opt/jumpserver directory or running 'jumpserver -v' or checking the web interface footer for version information.
    Affected if The installed version falls within the affected ranges: >= 2.4.0 and < 2.4.5, >= 2.5.0 and < 2.5.4, or >= 2.6.0 and < 2.6.2
  2. Locate the connection token API endpoint
    Examine the API documentation or reverse engineer the application routing to identify the endpoint responsible for creating connection tokens. This is typically found in the /api/ directory under endpoints related to 'terminal' or 'connect'.
    Affected if The endpoint exists and is reachable without requiring authentication or valid session tokens
  3. Test API access control
    Send an HTTP request to the token creation API endpoint without including any authentication headers, cookies, or tokens. Use a tool like curl to make an unauthenticated POST request to the suspected endpoint.
    Affected if The API accepts the request and returns a valid connection token without verifying the caller's identity or permissions
  4. Verify token usability
    If an unauthenticated request successfully generates a token, attempt to use that token to establish a connection to an internal asset or service that should require authorization.
    Affected if The token is accepted and provides access to sensitive infrastructure resources without proper authorization

A Jumpserver installation is affected if it runs a version before 2.4.5, 2.5.4, or 2.6.2 AND the connection token creation API can be invoked without authentication to obtain usable access tokens.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.4.5 / 2.5.4 / 2.6.2 or later
Fixed in 2.4.52.5.42.6.2
Interim mitigation

Upgrade Jumpserver to version 2.6.2, 2.5.4, 2.4.5 or later to obtain the security patch. Additionally, audit API endpoints for access control gaps and implement proper authentication/authorization checks on all token creation mechanisms.

Recommended fix High confidence

Upgrade to Jumpserver 2.6.2, 2.5.4, or 2.4.5 (or any later version in those respective branches)

  1. 1. Identify your current Jumpserver version by checking the installation or running the version command
  2. 2. Plan your upgrade: choose version 2.6.2 (or later 2.x), 2.5.4 (or later 2.5.x), or 2.4.5 (or later 2.4.x) depending on your current branch
  3. 3. Back up the Jumpserver database and configuration files before upgrading
  4. 4. Follow the official Jumpserver upgrade documentation for your installation method (Docker, Ansible, or manual)
  5. 5. Upgrade Jumpserver to your chosen fixed version (2.6.2, 2.5.4, or 2.4.5 or later)
  6. 6. Verify the upgrade was successful and the API access control is now properly enforced
Caveat Review release notes for any configuration changes or migration steps required between versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jumpserver Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-3169 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-3169 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data