# CVE-2024-3135: Cross-Site Request Forgery (CSRF) Vulnerability in mudler/localai

> Attackers can force victims to perform unauthorized resource-intensive actions on their LocalAI instance, leading to resource exhaustion and disk space consumption.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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:** 1 Apr 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-jhvf-7c85-3c9g, GO-2024-2705

## What is CVE-2024-3135?

CVE-2024-3135 is a medium-severity vulnerability in mudler/localai, published on 1 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

A Cross-Site Request Forgery (CSRF) vulnerability exists in the mudler/localai application, allowing attackers to craft malicious webpages that, when visited by a victim, perform unauthorized actions on the victim's local LocalAI instance without their consent. This vulnerability enables attackers to exhaust system resources, consume credits, and fill disk space by making numerous resource-intensive API calls, such as generating images or uploading files. The vulnerability stems from the application's acceptance of simple request content-types without requiring CSRF tokens or implementing other CSRF mitigation measures. Successful exploitation does not require network access to the vulnerable LocalAI environment.

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

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

3 open source packages ship an affected version, including github.com/go-skynet/LocalAI. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/go-skynet/LocalAI` | Go | All versions | None |
| `github.com/go-skynet/LocalAI` | Go | All versions to 2.7.0 | None |
| `github.com/go-skynet/LocalAI` | Go | All versions to 2.7.0 | None |

Products: Mudler Localai.

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

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

## Is CVE-2024-3135 being exploited?

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

## Other vulnerabilities in mudler/localai

- [CVE-2024-5181](https://insights.sbomify.com/CVE-2024-5181/): Command Injection in mudler/localai (critical 9.8)
- [CVE-2024-2029](https://insights.sbomify.com/CVE-2024-2029/): Command Injection in mudler/localai (critical 9.8)
- [CVE-2024-6983](https://insights.sbomify.com/CVE-2024-6983/): Remote Code Execution in mudler/localai (high 8.8)
- [CVE-2024-6868](https://insights.sbomify.com/CVE-2024-6868/): Arbitrary File Write in mudler/LocalAI (high 8.1)
- [CVE-2024-7010](https://insights.sbomify.com/CVE-2024-7010/): Timing Attack in mudler/localai (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-3135 is a medium-severity vulnerability in mudler/localai, published on 1 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-3135 exists.

Affected packages and fixed versions:
- github.com/go-skynet/LocalAI (Go): affected all versions; no fix listed
- github.com/go-skynet/LocalAI (Go): affected all versions up to 2.7.0; no fix listed
- github.com/go-skynet/LocalAI (Go): affected all versions up to 2.7.0; 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-3135/ (Markdown: https://insights.sbomify.com/CVE-2024-3135/index.md)
```

## Sources

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

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