← Back
CVE-2024-8769
Path Traversal in aim (CVE-2024-8769)
Summary
path traversal in aim (CVE-2024-8769). Data can be tampered with by attackers. Exploitable via ``LockManager.release_locks``.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-8769** has been found in aim.
Attackers can target a specific entry point like ``LockManager.release_locks`` over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: ?/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "aim CVE-2024-8769" on the vendor's site.
CVE-2024-8769 (aim) — CWE-22 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `LockManager.release_locks` / `run_hash`
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**Path traversal** (CWE-22) exists in aim. Attackers reach the vulnerable code path via ``LockManager.release_locks`` without authentication.
📍 Affected scope
aim — . Attack surface: `LockManager.release_locks` / `run_hash`.
🔥 Severity
Severity: ?. Data can be tampered with by attackers
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'aim' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'aim' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `aim` を grep し、稼働しているサービス・バージョンを把握する。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
aim
[{"type":"ECOSYSTEM","events":[{"introduced":"3.15.0"},{"last_affected":"3.27.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-8769
- advisory https://github.com/advisories/GHSA-4qcx-jx49-6qrh
- package https://github.com/aimhubio/aim
- package https://pypi.org/project/aim
- web https://github.com/aimhubio/aim/blob/bb76afe6e9a54364f322520cc4fea2679238f904/aim/sdk/lock_manager.py#L140
- web https://huntr.com/bounties/59d3472f-f581-4beb-a090-afd36a00ecf7