सापेक्ष पथ पारगमन (Relative Path Traversal) के माध्यम से मनमाना फ़ाइल विलोपन aimhubio/aim में

The LockManager.releaselocks function in aimhubio/aim is vulnerable to path traversal due to improper handling of the runhash parameter. This parameter, directly influenced by user input, is concatenated into a file path without proper sanitization. Consequently, an attacker can craft malicious requests to the Repo.closerun() method, accessible through the tracking server’s instruction API, to delete any file on the server's file system. This includes critical configuration files, logs, or even system binaries, potentially leading to complete system takeover. The ability to delete arbitrary files significantly expands the attack surface and increases the potential for severe consequences.

Organizations utilizing aimhubio/aim as a tracking server, particularly those with publicly exposed APIs or inadequate input validation, are at significant risk. Shared hosting environments where multiple users share the same server instance are especially vulnerable, as an attacker could potentially compromise the entire system through a single affected aimhubio/aim instance.

• python / server:

import os
import subprocess

# Check for suspicious file deletion attempts in logs
log_file = '/path/to/aimhubio/aim/logs/tracking_server.log'

with open(log_file, 'r') as f:
    for line in f:
        if 'delete' in line.lower() and 'run_hash' in line.lower():
            print(f'Potential path traversal attempt detected: {line}')

• linux / server:

# Monitor file system activity for unexpected deletions
journalctl -f -u aimhubio_aim | grep 'delete'

1. 2025-03-20Disclosure

   disclosure

1. आरक्षित2024-09-12
2. प्रकाशित2025-03-20
3. संशोधित2025-10-15
4. EPSS अद्यतन2026-04-02

While a patched version of aimhubio/aim is the recommended solution, immediate mitigation steps can be taken. First, restrict access to the tracking server instruction API to only authorized users and systems. Implement strict input validation on the run_hash parameter to prevent the injection of relative path components. Consider using a Web Application Firewall (WAF) to filter out malicious requests containing path traversal attempts. Regular monitoring of file system activity for unexpected deletions is also crucial. After upgrading, verify the fix by attempting a path traversal attack via the tracking server API and confirming that file deletion is prevented.