{"answers":{"affected":"3 open source packages ship an affected version, including clearml. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-24591 exists.","fix":"Upgrade clearml to 1.14.2 or later.","what":"CVE-2024-24591 is a high-severity path traversal vulnerability in Allegro.AI ClearML, published on 6 Feb 2024. 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-2024-24591 and fix it if it is affected.\n\nWhat it is: CVE-2024-24591 is a high-severity path traversal vulnerability in Allegro.AI ClearML, published on 6 Feb 2024. 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-2024-24591 exists.\n\nAffected packages and fixed versions:\n- clearml (PyPI): affected from 0.17.0 up to 1.14.1; no fix listed\n- clearml (PyPI): affected from 0.17.0 up to 1.14.1; no fix listed\n- clearml (PyPI): affected from 0.17.0; fixed in 1.14.2\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-24591/ (Markdown: https://insights.sbomify.com/CVE-2024-24591/index.md)","id":"CVE-2024-24591","markdown":"https://insights.sbomify.com/CVE-2024-24591/index.md","name":"CVE-2024-24591","record":{"aliases":["GHSA-m95h-p4gg-wfw3","PYSEC-2026-1258"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"ClearML client SDK","requires_auth":"low_privilege","summary":"A path traversal flaw in the ClearML client SDK allows attackers to write files to arbitrary locations via malicious datasets, potentially leading to code execution.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"HiddenLayer","cpe":[{"product":"clearml","vendor":"clear"}],"cvss":{"score":8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"A path traversal vulnerability in versions 1.4.0 to 1.14.1 of the client SDK of Allegro AI’s ClearML platform enables a maliciously uploaded dataset to write local or remote files to an arbitrary location on an end user’s system when interacted with.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Allegro AI ClearML path traversal vulnerability","id":"CVE-2024-24591","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"path_traversal","year":"2024"},"n_packages":3,"n_references":1,"next":{"headline":"Missing authorization in ClearML","id":"CVE-2024-24592"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0.17.0"],"last_affected":["1.14.1"],"package":"clearml","purl":null,"source":"GHSA-m95h-p4gg-wfw3"},{"ecosystem":"PyPI","fixed":[],"introduced":["0.17.0"],"last_affected":["1.14.1"],"package":"clearml","purl":"pkg:pypi/clearml","source":"GHSA-m95h-p4gg-wfw3"},{"ecosystem":"PyPI","fixed":["1.14.2"],"introduced":["0.17.0"],"last_affected":[],"package":"clearml","purl":"pkg:pypi/clearml","source":"PYSEC-2026-1258"}],"prev":{"headline":"Allegro AI ClearML vulnerable to deserialization of untrusted data","id":"CVE-2024-24590"},"products":["ClearML"],"published":"2024-02-06","related":[{"cvss_score":9.9,"headline":"Cross-site scripting in ClearML","id":"CVE-2024-24594","kev_date_added":null,"published":"2024-02-06"},{"cvss_score":9.8,"headline":"Missing authorization in ClearML","id":"CVE-2024-24592","kev_date_added":null,"published":"2024-02-06"},{"cvss_score":9.6,"headline":"Cross-site request forgery in ClearML","id":"CVE-2024-24593","kev_date_added":null,"published":"2024-02-06"},{"cvss_score":8,"headline":"Allegro AI ClearML vulnerable to deserialization of untrusted data","id":"CVE-2024-24590","kev_date_added":null,"published":"2024-02-06"},{"cvss_score":6,"headline":"Allegro AI ClearML Stores Credentials in Plaintext in MongoDB Instance","id":"CVE-2024-24595","kev_date_added":null,"published":"2024-02-05"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-05-15","vendors":["Allegro.AI"]},"summary":"A path traversal flaw in the ClearML client SDK allows attackers to write files to arbitrary locations via malicious datasets, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2024-24591/"}