Authenticated code execution via Ansible package overwrite
Published Jul 18, 2024 · Updated Mar 25, 2025
Arbitrary file write in JumpServer 3.0.0 through 3.10.11 allows remote authenticated users to execute code in the Celery container. A Job Center playbook can use Ansible's fetch module with flat output to overwrite ansible/init.py, which a later playbook loads as Python code. A low-privileged account with access to at least one host and Job Center is sufficient, and execution runs as root with database access.
Summary
What happened
Arbitrary file write in JumpServer 3.0.0 through 3.10.11 allows remote authenticated users to execute code in the Celery container. A Job Center playbook can use Ansible's fetch module with flat output to overwrite ansible/init.py, which a later playbook loads as Python code. A low-privileged account with access to at least one host and Job Center is sufficient, and execution runs as root with database access.
The record
- CVE
- CVE-2024-40629
- Published
- Jul 18, 2024
- Updated
- Mar 25, 2025
- Vendor
- JumpServer
- Product
- JumpServer
- Classifications
- CWE-22, T1059.006
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 18, 2024CVE publishedPublication date reported by the CVE source.
- Mar 25, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 3.0.0, < 3.10.12
- Affected versionversion=3.0.0 <3.10.12
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub advisory reproduction playbookproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo