# CVE-2024-6095: SSRF and Partial LFI in /models/apply Endpoint in mudler/localai

> An attacker can exploit SSRF and partial LFI in the /models/apply endpoint to access internal servers and read local files.

- **Severity:** Medium 5.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jul 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-fgv5-qx89-qjrh

## What is CVE-2024-6095?

CVE-2024-6095 is a medium-severity server-side request forgery vulnerability in mudler/localai, published on 6 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the /models/apply endpoint of mudler/localai versions 2.15.0 allows for Server-Side Request Forgery (SSRF) and partial Local File Inclusion (LFI). The endpoint supports both http(s):// and file:// schemes, where the latter can lead to LFI. However, the output is limited due to the length of the error message. This vulnerability can be exploited by an attacker with network access to the LocalAI instance, potentially allowing unauthorized access to internal HTTP(s) servers and partial reading of local files. The issue is fixed in version 2.17.

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 1 product.


Products: Mudler Localai.

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

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

## Is CVE-2024-6095 being exploited?

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

Public exploit code:

- https://github.com/Abdurahmon3236/-CVE-2024-6095 (github_poc): https://github.com/Abdurahmon3236/-CVE-2024-6095
- LocalAI - Partial Local File Read (nuclei): http/cves/2024/CVE-2024-6095.yaml

## 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-6095 and fix it if it is affected.

What it is: CVE-2024-6095 is a medium-severity server-side request forgery vulnerability in mudler/localai, published on 6 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-6095 exists.

Affected product: mudler/localai. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-6095/ (Markdown: https://insights.sbomify.com/CVE-2024-6095/index.md)
```

## Sources

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

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