{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-42819 exists.","fix":"No fix has been published for CVE-2023-42819 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-42819 is a high-severity path traversal vulnerability in jumpserver, published on 26 Sep 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-42819 and fix it if it is affected.\n\nWhat it is: CVE-2023-42819 is a high-severity path traversal vulnerability in jumpserver, published on 26 Sep 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-42819 exists.\n\nAffected product: jumpserver. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-42819/ (Markdown: https://insights.sbomify.com/CVE-2023-42819/index.md)","id":"CVE-2023-42819","markdown":"https://insights.sbomify.com/CVE-2023-42819/index.md","name":"CVE-2023-42819","record":{"aliases":["GHSA-ghg2-2whp-6m33"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"JumpServer bastion host","requires_auth":"low_privilege","summary":"Logged-in users can read or modify arbitrary system files via path traversal in JumpServer's playbook API.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"jumpserver","vendor":"fit2cloud"}],"cvss":{"score":8.9,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"JumpServer is an open source bastion host. Logged-in users can access and modify the contents of any file on the system. A user can use the 'Job-Template' menu and create a playbook named 'test'. Get the playbook id from the detail page, like 'e0adabef-c38f-492d-bd92-832bacc3df5f'. An attacker can exploit the directory traversal flaw using the provided URL to access and retrieve the contents of the file. `https://jumpserver-ip/api/v1/ops/playbook/e0adabef-c38f-492d-bd92-832bacc3df5f/file/?key=../../../../../../../etc/passwd` a similar method to modify the file content is also present. This issue has been addressed in version 3.6.5. Users are advised to upgrade. There are no known workarounds for this vulnerability.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2023-10-12","github_poc":1,"max_poc_stars":6,"metasploit":0,"nuclei":0,"refs":[{"date":"2023-10-12T08:45:46Z","kind":"github_poc","ref":"https://github.com/C1ph3rX13/CVE-2023-42819","stars":6,"title":"CVE-2023-42819"}],"tier":"weaponised"},"has_fix":false,"headline":"Path traversal in Jumpserver","id":"CVE-2023-42819","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Random seed leakage in Jumpserver","id":"CVE-2023-42820"},"packages":[],"prev":{"headline":"SSH public key login without private key challenge if mfa is enabled in jumpserver","id":"CVE-2023-42818"},"products":["jumpserver"],"published":"2023-09-26","related":[{"cvss_score":10,"headline":"Arbitrary File Read in Ansible Playbooks in Jumpserver","id":"CVE-2024-40628","kev_date_added":null,"published":"2024-07-18"},{"cvss_score":10,"headline":"Arbitrary File Write in Ansible Playbooks leads to RCE in Jumpserver","id":"CVE-2024-40629","kev_date_added":null,"published":"2024-07-18"},{"cvss_score":10,"headline":"JumpServer's insecure Ansible playbook validation leads to RCE in Celery","id":"CVE-2024-29201","kev_date_added":null,"published":"2024-03-29"},{"cvss_score":10,"headline":"JumpServer vulnerable to Jinja2 template injection in Ansible leads to RCE in Celery","id":"CVE-2024-29202","kev_date_added":null,"published":"2024-03-29"},{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2023-48193","kev_date_added":null,"published":"2023-11-28"},{"cvss_score":9.6,"headline":"JumpServer Connection Token Leak Vulnerability","id":"CVE-2025-62712","kev_date_added":null,"published":"2025-10-30"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-09-23","vendors":["jumpserver"]},"summary":"Logged-in users can read or modify arbitrary system files via path traversal in JumpServer's playbook API.","url":"https://insights.sbomify.com/CVE-2023-42819/"}