# CVE-2024-8736: Denial of Service (DoS) via Multipart Boundary in parisneo/lollms-webui

> Remote attackers can cause service unavailability in lollms-webui by exploiting multipart boundary parsing in file upload endpoints, bypassing CSRF protections.

- **Severity:** High 7.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/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:** 20 Mar 2025
- **Updated:** 4 Apr 2025
- **Also known as:** GHSA-vpg6-7cch-gq2j

## What is CVE-2024-8736?

CVE-2024-8736 is a high-severity denial of service vulnerability in parisneo/lollms-webui, published on 20 Mar 2025. 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 Denial of Service (DoS) vulnerability exists in multiple file upload endpoints of parisneo/lollms-webui version V12 (Strawberry). The vulnerability can be exploited remotely via Cross-Site Request Forgery (CSRF). Despite CSRF protection preventing file uploads, the application still processes multipart boundaries, leading to resource exhaustion. By appending additional characters to the multipart boundary, an attacker can cause the server to parse each byte of the boundary, ultimately leading to service unavailability. This vulnerability is present in the `/upload_avatar`, `/upload_app`, and `/upload_logo` endpoints.

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

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

It affects 1 product.


Products: Lollms Lollms Web Ui.

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

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

## Is CVE-2024-8736 being exploited?

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

## Other vulnerabilities in parisneo/lollms-webui

- [CVE-2024-2359](https://insights.sbomify.com/CVE-2024-2359/): Improper Neutralization of Special Elements used in an OS Command in parisneo/lollms-webui (critical 9.8)
- [CVE-2024-2360](https://insights.sbomify.com/CVE-2024-2360/): Path Traversal leading to Remote Code Execution in parisneo/lollms-webui (critical 9.8)
- [CVE-2024-4320](https://insights.sbomify.com/CVE-2024-4320/): Remote Code Execution due to LFI in '/install_extension' in parisneo/lollms-webui (critical 9.8)
- [CVE-2024-2358](https://insights.sbomify.com/CVE-2024-2358/): Path Traversal leading to Remote Code Execution in parisneo/lollms-webui (critical 9.8)
- [CVE-2024-4326](https://insights.sbomify.com/CVE-2024-4326/): Remote Code Execution via `/apply_settings` and `/execute_code` in parisneo/lollms-webui (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-8736 is a high-severity denial of service vulnerability in parisneo/lollms-webui, published on 20 Mar 2025. 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-8736 exists.

Affected product: parisneo/lollms-webui. 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-8736/ (Markdown: https://insights.sbomify.com/CVE-2024-8736/index.md)
```

## Sources

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

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