Live › vulnerability › CVE-2024-6829
Go to dashboardThe Aim Python package extracts uploaded tar archives with tarfile.extractall() without checking member paths, so a crafted archive can place files outside the intended directory. An attacker can overwrite critical files on the tracking server, for example by adding an SSH key for code execution.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-26 21:21 UTC, 1h before NVD. All times on this page are UTC.
Teams running the Aim tracking server (aimhubio/aim) at version 3.19.3 or earlier, especially where the server accepts repository or run uploads from others. Installs where the server is only used locally by one trusted user are less exposed.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| aim | pypi | <= 3.19.3 | – |
| aimstack aim | vendor | = 3.19.3 | – |
pip show aim and compare the version against 3.19.3aim to a version newer than 3.19.3; the fixed version is unknown from the sourcesEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
A vulnerability in aimhubio/aim version 3.19.3 allows an attacker to exploit the tarfile.extractall() function to extract the contents of a maliciously crafted tarfile to arbitrary locations on the host server. The attacker can control repo.path and run_hash to bypass directory existence checks and extract files to unintended locations, potentially overwriting critical files. This can lead to arbitrary data being written to arbitrary locations on the remote tracking server, which could be used for further attacks such as writing a new SSH key to the target server.
This page as .md · .json · in your agent: get_signal("CVE-2024-6829")
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.