{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-32317 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-32317 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-32317 is a medium-severity path traversal vulnerability in Autolab, published on 26 May 2023. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-32317 and fix it if it is affected.\n\nWhat it is: CVE-2023-32317 is a medium-severity path traversal vulnerability in Autolab, published on 26 May 2023. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-32317 in the wild and no public exploit code.\n\nAffected product: Autolab. 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-32317/ (Markdown: https://insights.sbomify.com/CVE-2023-32317/index.md)","id":"CVE-2023-32317","markdown":"https://insights.sbomify.com/CVE-2023-32317/index.md","name":"CVE-2023-32317","record":{"aliases":["GHSA-h8g5-vhm4-wx6g"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Autolab course management","requires_auth":"high_privilege","summary":"Authenticated instructors can achieve arbitrary file write and potential code execution by uploading malicious tar archives to the MOSS cheat checker.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"autolab","vendor":"autolabproject"}],"cvss":{"score":6.7,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Autolab is a course management service that enables auto-graded programming assignments. A Tar slip vulnerability was found in the MOSS cheat checker functionality of Autolab. To exploit this vulnerability an authenticated attacker with instructor permissions needs to upload a specially crafted Tar file. Both \"Base File Tar\" and \"Additional file archive\" can be fed with Tar files that contain paths outside their target directories (e.g.,  `../../../../tmp/tarslipped2.sh`). When the MOSS cheat checker is started the files inside of the archives are expanded to the attacker-chosen locations. This issue may lead to arbitrary file write within the scope of the running process.  This issue has been addressed in version 2.11.0. Users are advised to upgrade.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Autolab tar slip in cheat checker functionality (`GHSL-2023-082`)","id":"CVE-2023-32317","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"User session not correctly destroyed on logout","id":"CVE-2023-32318"},"packages":[],"prev":{"headline":"Users can add themselves to any organization in CloudExplorer Lite","id":"CVE-2023-32316"},"products":["Autolab"],"published":"2023-05-26","related":[{"cvss_score":8.8,"headline":"Autolab is vulnerable to remote code execution (RCE) via MOSS functionality","id":"CVE-2022-41955","kev_date_added":null,"published":"2023-01-14"},{"cvss_score":7.6,"headline":"Cross-site Scripting (XSS) - Stored in autolab/autolab","id":"CVE-2022-0936","kev_date_added":null,"published":"2022-04-11"},{"cvss_score":7.1,"headline":"download_all_submissions allows student to download another student's submissions in Autolab","id":"CVE-2024-53258","kev_date_added":null,"published":"2024-11-25"},{"cvss_score":7.1,"headline":"Autolab Has Misconfigured Reset Password Permissions","id":"CVE-2024-49376","kev_date_added":null,"published":"2024-10-25"},{"cvss_score":6.8,"headline":"Course Roster vulnerable to CSV Injection in Autolab","id":"CVE-2024-53260","kev_date_added":null,"published":"2024-11-27"},{"cvss_score":6.7,"headline":"Autolab tar slip in Install Assessment functionality (`GHSL-2023-081`)","id":"CVE-2023-32676","kev_date_added":null,"published":"2023-05-26"}],"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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-02","vendors":["autolab"]},"summary":"Authenticated instructors can achieve arbitrary file write and potential code execution by uploading malicious tar archives to the MOSS cheat checker.","url":"https://insights.sbomify.com/CVE-2023-32317/"}