CVE-2024-8061: Aim allows denial of service due to no timeouts for some tracking server endpoints
In version 3.23.0 of aimhubio/aim, certain methods that request data from external servers do not have set timeouts, causing the server to wait indefinitely for a response. This can lead to a denial of service, as the tracking server does not respond to other requests while waiting.
Published Mar 20, 2025 · Updated Oct 15, 2025
Affected packages
aim
- Ecosystem
- PyPI
- Affected
- <= 3.23.0
- Fixed in
- No patched version yet
- Check
pip show aim
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
In version 3.23.0 of aimhubio/aim, certain methods that request data from external servers do not have set timeouts, causing the server to wait indefinitely for a response. This can lead to a denial of service, as the tracking server does not respond to other requests while waiting. The issue arises in the client used by the aim tracking server to communicate with external resources, specifically in the _run_read_instructions method and similar calls without timeouts.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2025-51464
Aim vulnerable to Cross-site Scripting
medium5.3No fixJul 22, 2025CVE-2025-5321
Aim Vulnerable to Sandbox Escape Leading to Remote Code Execution
low6.3No fixMay 29, 2025CVE-2024-10110
Aim Vulnerable to Denial of Service (DoS)
high7.5No fixMar 20, 2025CVE-2024-12777
Aim vulnerable to Synchronous Access of Remote Resource without Timeout
medium5.9No fixMar 20, 2025CVE-2024-12778
Aim Uncontrolled Resource Consumption vulnerability
high7.5No fixMar 20, 2025CVE-2024-6483
Aim Relative Path Traversal vulnerability
medium5.3No fixMar 20, 2025
