CVE-2024-40628
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 Privileged Access Management (PAM) tool that provides DevOps and IT teams with on-demand and secure access to SSH, RDP, Kubernetes, Database and RemoteApp endpoints through a web browser. An attacker can exploit the ansible playbook to read arbitrary files in the celery container, leading to sensitive information disclosure. The Celery container runs as root and has database access, allowing the attacker to steal all secrets for hosts, create a new JumpServer account with admin privileges, or manipulate the database in other ways. This issue has been addressed in release versions 3.10.12 and 4.0.0. It is recommended to upgrade the safe versions. There is no known workarounds for this vulnerability.
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 confidenceJumpServer contains a path traversal vulnerability in its ansible playbook functionality within the celery container. Since the celery container runs as root and has direct database access, an attacker can read arbitrary files, exfiltrate all host secrets, create new administrative accounts, or manipulate the database at will.
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.12CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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.
-
Confirm JumpServer is deployedInspect running containers or processes for jump-server, jms, or related service names using 'docker ps' or 'kubectl get pods'. Check for default JumpServer ports (8080, 2222) listening.Affected if JumpServer containers or services are running in the environment
-
Identify installed JumpServer versionCheck the docker image tag or JumpServer configuration file for version information. Common locations: 'docker images', 'docker inspect <container>', or check /opt/jumpserver/config.yml if accessible.Affected if The version falls within >= 3.0.0 and < 3.10.12
-
Verify celery container existsList all containers in the JumpServer deployment and confirm a container named 'celery' or 'jms_celery' is running. The vulnerability exists specifically within this component.Affected if The celery container is present and running
-
Check if ansible playbook feature is enabledInspect JumpServer settings or configuration for ansible-related modules or playbook execution capabilities. Look for 'ansible' in enabled features or application settings.Affected if Ansible playbook functionality is enabled in JumpServer settings
-
Review celery container logs for path traversal indicatorsExecute 'docker logs <celery_container>' or equivalent to search for suspicious file access patterns, unusual path references, or indicators of unauthorized file reads.Affected if Logs show access to unexpected system files or directories outside normal ansible operations
The environment is affected if JumpServer version is between 3.0.0 and 3.10.12, the celery container is running, and ansible playbook functionality is enabled.
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.12
Upgrade JumpServer to version 3.10.12 or 4.0.0 (or later). No workarounds exist; immediate patching is required given the critical severity and full system compromise potential.
Upgrade to JumpServer version 3.10.12 or 4.0.0
- Backup the current JumpServer installation and database
- Stop the JumpServer services
- Upgrade JumpServer to version 3.10.12 or 4.0.0 using the official upgrade method for your deployment (e.g., Docker, Kubernetes, or source installation)
- Verify the new version is installed by checking the version number
- Restart all JumpServer services
- Confirm the vulnerability is resolved by verifying the ansible playbook path traversal is no longer exploitable
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-40628 — 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-40628 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