Critical · published March 20, 2025
🚨 A single malicious parameter can lead to arbitrary file deletion! This sneaky vulnerability in aimhubio/aim’s `LockManager.release_locks` function can let an attacker wipe any file on your server! 🔥 Think of it like giving someone a key to your storage room but not checking what they actually put in there. If they ask for a specific item, they could just as easily ask to take the whole shelf down! With this vulnerability, an attacker could execute a command that permanently deletes vital files from your system, resulting in potential data loss or service disruption. Imagine losing important project files or configurations just because of a poorly sanitized input! This could lead to a catastrophic halt in operations!
Think of it like giving someone a key to your storage room but not checking what they actually put in there. If they ask for a specific item, they could just as easily ask to take the whole shelf down! The vulnerability arises because the `run_hash` parameter is directly concatenated into a file path without proper normalization, allowing attackers to traverse directories and specify any file for deletion. The exploit occurs through the `Repo._close_run()` method, which is accessible via the tracking server’s API.
With this vulnerability, an attacker could execute a command that permanently deletes vital files from your system, resulting in potential data loss or service disruption. Imagine losing important project files or configurations just because of a poorly sanitized input! This could lead to a catastrophic halt in operations! Upgrade to the latest version of aimhubio/aim where this vulnerability is patched. Ensure that input parameters such as `run_hash` are properly sanitized and validated to prevent path traversal attacks. It’s best to implement strict file deletion policies as an additional precaution. You've got this! By taking these steps, you'll be locking down your system and protecting it from this serious threat! 🛡️