# CVE-2024-40628: Arbitrary File Read in Ansible Playbooks in Jumpserver

> Attackers can read arbitrary files via Ansible playbooks, exposing secrets and enabling admin account creation in JumpServer.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jul 2024
- **Updated:** 25 Mar 2025
- **Also known as:** GHSA-rpf7-g4xh-84v9

## What is CVE-2024-40628?

CVE-2024-40628 is a critical path traversal vulnerability in jumpserver, published on 18 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

JumpServer 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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2024-40628?

It affects 1 product.


Products: Fit2cloud Jumpserver.

## How do I fix CVE-2024-40628?

No fix has been published for CVE-2024-40628 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-40628 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-40628 exists.

## Other vulnerabilities in jumpserver

- [CVE-2024-40629](https://insights.sbomify.com/CVE-2024-40629/): Arbitrary File Write in Ansible Playbooks leads to RCE in Jumpserver (critical 10.0)
- [CVE-2024-29201](https://insights.sbomify.com/CVE-2024-29201/): JumpServer's insecure Ansible playbook validation leads to RCE in Celery (critical 10.0)
- [CVE-2024-29202](https://insights.sbomify.com/CVE-2024-29202/): JumpServer vulnerable to Jinja2 template injection in Ansible leads to RCE in Celery (critical 10.0)
- [CVE-2023-48193](https://insights.sbomify.com/CVE-2023-48193/): Security feature bypass in n/a (critical 9.8)
- [CVE-2025-62712](https://insights.sbomify.com/CVE-2025-62712/): JumpServer Connection Token Leak Vulnerability (critical 9.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-40628 and fix it if it is affected.

What it is: CVE-2024-40628 is a critical path traversal vulnerability in jumpserver, published on 18 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-40628 exists.

Affected product: jumpserver. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-40628/ (Markdown: https://insights.sbomify.com/CVE-2024-40628/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-40628
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-40628
- OSV: https://osv.dev/vulnerability/CVE-2024-40628

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-40628/
Summaries are generated and may contain mistakes; the official description above is the record.