Aim path traversal in LockManager.release_locks
A vulnerability in the `LockManager.release_locks` function in aimhubio/aim (commit bb76afe) allows for arbitrary file deletion through relative path traversal. The `run_hash` parameter, which is user-controllable, is concatenated without normalization as part of a path used to specify file deletion. This vulnerability is exposed through the `Repo._close_run()` method, which is accessible via the tracking server instruction API. As a result, an attacker can exploit this to delete any arbitrary file on the machine running the tracking server.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2024-8769US | critical9.1 | — | ||
A vulnerability in the `LockManager.release_locks` function in aimhubio/aim (commit bb76afe) allows for arbitrary file deletion through relative path traversal. The `run_hash` para… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/advisories/GHSA-4qcx-jx49-6qrhADVISORY
- https://github.com/aimhubio/aimPACKAGE
- https://github.com/aimhubio/aim/blob/bb76afe6e9a54364f322520cc4fea2679238f904/aim/sdk/lock_manager.py#L140WEB
- https://huntr.com/bounties/59d3472f-f581-4beb-a090-afd36a00ecf7WEB
- https://nvd.nist.gov/vuln/detail/CVE-2024-8769ADVISORY
- https://pypi.org/project/aimPACKAGE
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan