dbcve.org
JumpserverApplication · Fit2cloud

CVE-2024-29020

MEDIUM · 5.3 CVSS v3.1 Published 2024-03-29
Fix available
A fix is available. Upgrade to 3.10.6 or later.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable 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
JumpServer is an open source bastion host and an operation and maintenance security audit system. An authorized attacker can obtain sensitive information contained within playbook files if they manage to learn the playbook_id of another user. This breach of confidentiality can lead to information disclosure and exposing sensitive data. This vulnerability is fixed in v3.10.6.

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 · high confidence

JumpServer contains an access control vulnerability where an authenticated attacker can access sensitive information in playbook files belonging to other users by leveraging the playbook_id parameter. This Insecure Direct Object Reference (IDOR) allows unauthorized cross-user access to confidential playbook content containing potentially sensitive data.

MitigationUpgrade to JumpServer v3.10.6 or later. Review and rotate any credentials or sensitive data that may have been exposed in playbook files, and implement additional access controls to prevent unauthorized cross-user resource access.

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:>= 3.0.0, < 3.10.6

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 the installed JumpServer version
    Run 'jumpserver --version' or check the version file in the JumpServer installation directory, typically found in /opt/jumpserver or the installation root path
    Affected if The version is 3.0.0 through 3.10.5 (inclusive)
  2. Verify the playbook feature is accessible
    Log into the JumpServer web interface or API and navigate to the playbook management section to confirm playbooks can be created, viewed, or edited
    Affected if Playbook functionality is enabled and accessible to authenticated users
  3. Confirm user authentication is enabled
    Check that JumpServer authentication is properly configured and that user accounts exist in the system
    Affected if Users can authenticate to the platform and access their own resources
  4. Test for IDOR on playbook access
    Using an authenticated account, attempt to access a playbook by modifying the playbook_id parameter in API requests or URLs to reference a playbook owned by a different user
    Affected if You can successfully view or retrieve playbook content belonging to another user without proper authorization checks
  5. Review audit logs for cross-user playbook access
    Check JumpServer audit logs for any entries showing playbook access from user A accessing user B's playbook_id, particularly repeated or bulk access patterns
    Affected if Audit logs show playbook access events where the requesting user differs from the playbook owner

You are affected if your JumpServer version is between 3.0.0 and 3.10.5 inclusive and the playbook feature is accessible to authenticated users who can potentially access other users' playbook files.

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 3.10.6 or later
Fixed in 3.10.6
Interim mitigation

Upgrade to JumpServer v3.10.6 or later. Review and rotate any credentials or sensitive data that may have been exposed in playbook files, and implement additional access controls to prevent unauthorized cross-user resource access.

Recommended fix High confidence

v3.10.6

  1. 1. Backup your current JumpServer installation and database
  2. 2. Upgrade JumpServer to version 3.10.6 or later
  3. 3. Verify the upgrade was successful by checking the version number
  4. 4. Test that the authorization bypass is fixed by attempting to access playbook files with different user contexts
Caveat Review the changelog between your current version and 3.10.6 for any configuration or feature changes that may affect your deployment

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

Fix this in Jumpserver Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-29020 — 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-2024-29020 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