CSRF in Aimhubio Aimhubio/aim
CVE-2024-2196
aimhubio/aim is vulnerable to Cross-Site Request Forgery (CSRF), allowing attackers to perform actions such as deleting runs, updating data, and stealing data like log records and notes without the user's consent. The vulnerability stems from the lack of CSRF and CORS protection in the aim dashboard. An attacker can exploit this by tricking a user into executing a malicious script that sends unauthorized requests to the aim server, leading to potential data loss and unauthorized data manipulation.
Vulnerability class: CSRF (Cross-Site Request Forgery)
EPSS: 0.006 (44.6th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 8.8 (High). Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.
Affected products
- Aimhubio Aimhubio/aim — versions unspecified
- Aimstack Aim — versions 3.17.5
Weakness classification (CWE)
Public proof-of-concept exploits
References
- security@huntr.dev (Exploit, Third Party Advisory)
Frequently asked questions
- What is CVE-2024-2196?
- CVE-2024-2196 is a high-severity vulnerability in Aimhubio Aimhubio/aim, classified under Cross-Site Request Forgery (CSRF). CVSS score: 8.8/10. Published 2024-04-10.
- How severe is CVE-2024-2196?
- High severity. CVSS v3 base score is 8.8 out of 10.
- Is CVE-2024-2196 known to be exploited?
- 2 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.