Skip to content
Heist/ feed
Back to feed
Critical

Arbitrary File Deletion via Relative Path Traversal in aimhubio/aim

Type: advisorySources: OSV

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.

Products
Not specified
Affected versions
Not specified
Fixed versions
Not specified
CVEs
CVE-2024-8769
Confirmed fixed CVEs
Not specified
Updated in this feed
8 Nov 2026, 00:17 UTC · Revision 1

Source evidence

Arbitrary File Deletion via Relative Path Traversal in aimhubio/aim

core-osv · Original source

Published 20 Mar 2025, 10:11 UTC

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.

osv:CVE-2024-8769
Complete source record
{
  "id": "1bd9974284d122320df9202460ee459c46732c1ccd9027ead8497d0d33e8b20b",
  "url": "https://osv.dev/vulnerability/CVE-2024-8769",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "Arbitrary File Deletion via Relative Path Traversal in aimhubio/aim",
    "summary": "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.",
    "evidence": "osv:CVE-2024-8769",
    "products": [],
    "severity": "critical",
    "structured": {
      "id": "CVE-2024-8769",
      "aliases": [
        "CVE-2024-8769",
        "GHSA-4qcx-jx49-6qrh",
        "PYSEC-2026-258"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://github.com/aimhubio/aim",
              "type": "GIT",
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "fixed": "bb76afe6e9a54364f322520cc4fea2679238f904"
                }
              ],
              "database_specific": {
                "extracted_events": [
                  {
                    "cpe": "cpe:2.3:a:aimstack:aim:*:*:*:*:*:*:*:*",
                    "range": [
                      {
                        "introduced": "0"
                      },
                      {
                        "fixed": "3.24.0"
                      }
                    ],
                    "source": "CPE_RANGE"
                  }
                ]
              }
            }
          ],
          "versions": [
            "v3.23.0",
            "v3.22.0",
            "v3.21.0",
            "v3.20.1",
            "v3.19.1",
            "v3.19.0",
            "v3.18.1",
            "v3.17.5",
            "v3.17.4",
            "v3.17.3",
            "v3.17.2",
            "v3.17.1",
            "v3.17.0",
            "v3.5.0",
            "v3.4.0",
            "v3.3.2",
            "v3.3.1",
            "v3.3.0",
            "v3.2.0",
            "v3.1.1",
            "v3.1.0",
            "v3.0.2",
            "v3.0.1",
            "v3.0.0",
            "v3.0.0-beta6",
            "v3.0.0-beta5",
            "v2.7.0",
            "v2.6.0",
            "v2.5.0",
            "v2.4.0",
            "v2.3.0",
            "v2.2.0",
            "v2.1.6",
            "pre-launch",
            "v1.2.7rc1",
            "v1.1.1",
            "v1.1.0",
            "v1.0.0",
            "v0.2.6",
            "v0.2.5",
            "v0.2.4",
            "v0.2.3",
            "v0.2.2",
            "v0.2.1",
            "v0.2.0",
            "v0.1.1",
            "v0.1.0"
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-8769.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:51.939915648Z",
      "provider": "osv",
      "references": [
        "https://huntr.com/bounties/59d3472f-f581-4beb-a090-afd36a00ecf7",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/8xxx/CVE-2024-8769.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2024-8769"
      ],
      "provider_metadata": {
        "cwe_ids": [
          "CWE-22"
        ],
        "cna_assigner": "@huntr_ai",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/8xxx/CVE-2024-8769.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2024-8769",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 520900,
  "published_at": "2025-03-20T10:11:22.123+00:00"
}