{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-28189 exists.","fix":"No fix has been published for CVE-2024-28189 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-28189 is a critical path traversal vulnerability in judge0, published on 18 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-28189 and fix it if it is affected.\n\nWhat it is: CVE-2024-28189 is a critical path traversal vulnerability in judge0, published on 18 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-28189 exists.\n\nAffected product: judge0. 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-2024-28189/ (Markdown: https://insights.sbomify.com/CVE-2024-28189/index.md)","id":"CVE-2024-28189","markdown":"https://insights.sbomify.com/CVE-2024-28189/index.md","name":"CVE-2024-28189","record":{"aliases":[],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Code execution system","requires_auth":"none","summary":"Attackers can escape the sandbox by exploiting symlink handling in chown operations, leading to arbitrary file modification and potential code execution.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":10,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-61","name":"UNIX Symbolic Link (Symlink) Following"},{"id":"CWE-59","name":"Improper Link Resolution Before File Access"}],"description":"Judge0 is an open-source online code execution system. The application uses the UNIX chown command on an untrusted file within the sandbox. An attacker can abuse this by creating a symbolic link (symlink) to a file outside the sandbox, allowing the attacker to run chown on arbitrary files outside of the sandbox. This vulnerability is not impactful on it's own, but it can be used to bypass the patch for CVE-2024-28185 and obtain a complete sandbox escape. This vulnerability is fixed in 1.13.1.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2024-03-04","github_poc":0,"max_poc_stars":null,"metasploit":1,"nuclei":0,"refs":[{"date":"2024-03-04","kind":"metasploit","ref":"exploit/linux/http/judge0_sandbox_escape_cve_2024_28189","stars":null,"title":"Judge0 sandbox escape"}],"tier":"weaponised"},"has_fix":false,"headline":"Judge0 vulnerable to Sandbox Escape Patch Bypass via chown running on Symbolic Link","id":"CVE-2024-28189","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2024"},"n_packages":0,"n_references":4,"next":{"headline":"Contao core bundle vulnerable to cross site scripting in the file manager","id":"CVE-2024-28190"},"packages":[],"prev":{"headline":"jupyter-scheduler's endpoint is missing authentication","id":"CVE-2024-28188"},"products":["judge0"],"published":"2024-04-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"BSD-3-Clause","name":"Metasploit"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["judge0"]},"summary":"Attackers can escape the sandbox by exploiting symlink handling in chown operations, leading to arbitrary file modification and potential code execution.","url":"https://insights.sbomify.com/CVE-2024-28189/"}