CVE-2024-29024
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 · uneditedJumpServer is an open source bastion host and an operation and maintenance security audit system. An authenticated user can exploit the Insecure Direct Object Reference (IDOR) vulnerability in the file manager's bulk transfer by manipulating job IDs to upload malicious files, potentially compromising the integrity and security of the system. 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 · moderate confidenceJumpServer contains an Insecure Direct Object Reference (IDOR) vulnerability in its file manager's bulk transfer functionality. An authenticated attacker can manipulate job IDs to upload malicious files to the system, potentially compromising system integrity.
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>= 3.0.0, < 3.10.6CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Check JumpServer versionAccess the JumpServer admin interface and navigate to the system information page, or run 'jumpserverctl version' if CLI access is available. Compare the installed version number against the affected range (>= 3.0.0 and < 3.10.6).Affected if The installed version falls within 3.0.0 to 3.10.5 inclusive.
-
Verify file manager module is enabledLog into the JumpServer admin panel and navigate to the system settings or feature configuration section. Look for the file manager or storage management module status.Affected if The file manager module is enabled and accessible to users.
-
Confirm bulk transfer feature is accessibleAs an authenticated user (non-admin), access the file manager interface and check if bulk transfer or batch file upload functionality is present and operational.Affected if Bulk transfer functionality is available to authenticated users.
-
Inspect job creation permissionsReview the user or user group permissions in the JumpServer admin panel under the file manager or job permissions settings. Check if standard users can create file transfer jobs.Affected if Authenticated users have permissions to create file transfer jobs.
Your environment is affected if JumpServer version is between 3.0.0 and 3.10.5 and the file manager bulk transfer feature is enabled for authenticated users.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.10.6
Upgrade JumpServer to v3.10.6 or later to patch the vulnerability. Until patched, restrict file transfer permissions to essential personnel only and monitor bulk transfer operations for suspicious activity.
v3.10.6
- Ensure you have a backup of your current JumpServer installation and database
- Review JumpServer upgrade documentation for your deployment method (Docker, Kubernetes, or source)
- Pull the latest JumpServer v3.10.6 release or update your deployment configuration to use version 3.10.6
- Stop the current JumpServer services
- Apply the database migrations if any are required for v3.10.6
- Start the JumpServer v3.10.6 services
- Verify the upgrade was successful by checking the version number in the web UI or via CLI
- Test the file manager bulk transfer functionality to confirm the IDOR vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-29024 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-29024 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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