Aim Pfadüberschreitungs-Schwachstelle

The vulnerability lies in the LocalFileManager._cleanup function, which is responsible for deleting files based on a user-provided glob-pattern. The function fails to adequately validate that the matched files reside within the intended directory managed by LocalFileManager. Consequently, a malicious actor can construct a glob-pattern that targets files outside of this directory, leading to unauthorized deletion of sensitive data. This could include configuration files, application code, or even system files, potentially disrupting the entire tracking server and compromising its integrity. The potential impact extends beyond data loss, as an attacker could potentially gain control over the server by deleting critical components.

Organizations and individuals utilizing aimhubio/aim versions 3.22.0 and earlier, particularly those running the tracking server in environments with limited access controls or where the file cleanup functionality is enabled without proper validation, are at significant risk. Shared hosting environments where multiple users have access to the aimhubio/aim installation are also particularly vulnerable.

• python / server:

import os
import glob

def check_file_deletion(directory, pattern):
    try:
        files = glob.glob(os.path.join(directory, pattern))
        for file in files:
            if not file.startswith(directory):
                print(f"Potential Path Traversal: File {file} outside of directory {directory}")
    except Exception as e:
        print(f"Error during glob check: {e}")

# Example usage (replace with actual directory and pattern)
directory = '/path/to/aimhubio/aim/data' # Replace with the actual data directory
patter = '*/temp/*' # Replace with the pattern being used
check_file_deletion(directory, pattern)

1. 2025-03-20Disclosure

   disclosure

1. Reserviert2024-07-17
2. Veröffentlicht2025-03-20
3. Geändert2025-03-21
4. EPSS aktualisiert2026-04-02

While a patched version is pending, several mitigation strategies can be implemented to reduce the risk. The most immediate step is to restrict access to the file deletion functionality to trusted users only. Implement strict input validation on the glob-pattern, ensuring it adheres to a predefined whitelist of allowed characters and patterns. Consider using a more secure file deletion mechanism that explicitly verifies the file path before deletion. As a temporary workaround, you could disable the file cleanup functionality entirely if it's not essential. Monitor system logs for any suspicious file deletion activity. After a future upgrade, confirm the fix by attempting to delete a file outside the intended directory using a crafted glob-pattern; the operation should be denied.