aimhubio/aim version 3.22.0 contains a Cross-Site Request Forgery (CSRF) vulnerability in the tracking server. The vulnerability is due to overly permissive CORS settings, allowing cross-origin requests from all origins. This enables CSRF attacks on all endpoints of the tracking server, which can be chained with other existing vulnerabilities such as remote code execution, denial of service, and arbitrary file read/write.
The Aim tracking server is configured with overly open CORS (Cross-Origin Resource Sharing) settings, which allows sending cross-origin requests from any domain. An attacker can trick a logged-in user into visiting a malicious website, which will send forged HTTP requests on their behalf to all endpoints of the tracking server. The CSRF vulnerability can then be chained with other existing flaws in the product, such as remote code execution (RCE), denial of service (DoS), and arbitrary file read and write.
An attacker can, through a victim, perform unauthorized operations on the tracking server, including potentially executing remote code (RCE), triggering denial of service (DoS), or reading and writing arbitrary files on the server — depending on which other vulnerabilities the CSRF is combined with.
Patches available from the vendor should be applied in accordance with the references. It is also recommended to restrict access to the tracking server exclusively to trusted networks and properly configure CORS policy to allow requests only from trusted domains.
Aimstack Aim version 3.22.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:HAimstack Aim
APPAimstack3.22.0
Related vulnerabilities
Aimstack Aim: path traversal umożliwiający usunięcie dowolnego pliku
Path traversal w Aimstack Aim – zapis plików w dowolnej lokalizacji serwera
Nadpisywanie plików i RCE w Aimstack Aim przez funkcję _backup_run
RCE w Aimstack Aim – wykonanie kodu przez parametr query w API
Path Traversal in restore_run_backup() in AIM 3.28.0 allows remote attackers to write arbitrary files to the s...