# CVE-2024-2196: CSRF Vulnerability in aimhubio/aim

> Attackers can trick users into deleting runs or stealing data via CSRF due to missing protections in the AIM dashboard.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Apr 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-99w2-67h8-5948, PYSEC-2026-1084

## What is CVE-2024-2196?

CVE-2024-2196 is a high-severity vulnerability in aimhubio/aim, published on 10 Apr 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2024-2196?

3 open source packages ship an affected version, including aim. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `aim` | PyPI | All versions to 3.17.5 | None |
| `aim` | PyPI | All versions to 3.17.5 | None |
| `aim` | PyPI | All versions to 3.17.5 | None |

Products: Aimstack Aim.

## How do I fix CVE-2024-2196?

No fix has been published for CVE-2024-2196 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-2196 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-2196 exists.

## Other vulnerabilities in aimhubio/aim

- [CVE-2024-6396](https://insights.sbomify.com/CVE-2024-6396/): Arbitrary File Overwrite and Data Exfiltration in aimhubio/aim (critical 9.8)
- [CVE-2024-2195](https://insights.sbomify.com/CVE-2024-2195/): Remote Code Execution in aimhubio/aim (critical 9.8)
- [CVE-2024-6829](https://insights.sbomify.com/CVE-2024-6829/): Arbitrary File Overwrite through tarfile-extraction in aimhubio/aim (critical 9.1)
- [CVE-2024-8769](https://insights.sbomify.com/CVE-2024-8769/): Arbitrary File Deletion via Relative Path Traversal in aimhubio/aim (critical 9.1)
- [CVE-2025-51464](https://insights.sbomify.com/CVE-2025-51464/): Aim vulnerable to Cross-site Scripting (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-2196 and fix it if it is affected.

What it is: CVE-2024-2196 is a high-severity vulnerability in aimhubio/aim, published on 10 Apr 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-2196 exists.

Affected packages and fixed versions:
- aim (PyPI): affected all versions up to 3.17.5; no fix listed
- aim (PyPI): affected all versions up to 3.17.5; no fix listed
- aim (PyPI): affected all versions up to 3.17.5; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-2196/ (Markdown: https://insights.sbomify.com/CVE-2024-2196/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-2196
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-2196
- OSV: https://osv.dev/vulnerability/CVE-2024-2196

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-2196/
Summaries are generated and may contain mistakes; the official description above is the record.