6 matches found
CVE-2024-2195
CVE-2024-2195 affects aimhubio/aim (versions ≥ 3.0.0). The issue is in the REST endpoint “/api/runs/search/run/” where the run_search_api in aim/web/api/runs/views.py fails to properly restrict access to the RunView object, allowing arbitrary code execution via the query parameter. Impact is high...
CVE-2024-8769
CVE-2024-8769 affects aimhubio/aim where the LockManager.release_locks function concatenates a user-controlled run_hash into a path, enabling relative path traversal that can delete arbitrary files. The flaw is exposed through Repo._close_run() via the tracking server instruction API, potentially...
CVE-2024-6396
An vulnerability in the _backup_run function of aimhubio/aim 3.19.3 allows remote attackers to manipulate run_hash and repo.path to create/write arbitrary files on the host and exfiltrate data, with potential for denial of service, data loss, or remote code execution. Confirmed by connected sourc...
CVE-2025-5321
The CVE-2025-5321 entry affects aimhubio Aim up to 3.29.1, targeting the RestrictedPythonQuery function in /aim/storage/query.py (run_view Object Handler). The vulnerability arises from manipulation of the argument (Query/Abfrage) that can lead to elevated privileges and sandbox issues, enabling ...
CVE-2024-6829
CVE-2024-6829 affects aimhubio/aim 3.19.3. The vulnerability arises in tarfile.extractall(), allowing an attacker-controlled tarfile to be extracted to arbitrary locations on the host by manipulating repo.path and run_hash. This bypasses directory existence checks and can result in arbitrary file...
CVE-2024-7760
CVE-2024-7760 affects aimhubio/aim (v3.22.0) where the tracking server is vulnerable to Cross‑Site Request Forgery (CSRF) due to overly permissive CORS settings that allow cross-origin requests from all origins. This vulnerability enables CSRF on all endpoints of the tracking server and can be ch...