# CVE-2024-4322: Path Traversal in parisneo/lollms-webui

> Attackers can traverse directories via the category parameter to list system folders, causing information disclosure in lollms-webui.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 16 May 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-482r-2hv2-p3x7

## What is CVE-2024-4322?

CVE-2024-4322 is a high-severity path traversal vulnerability in parisneo/lollms-webui, published on 16 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A path traversal vulnerability exists in the parisneo/lollms-webui application, specifically within the `/list_personalities` endpoint. By manipulating the `category` parameter, an attacker can traverse the directory structure and list any directory on the system. This issue affects the latest version of the application. The vulnerability is due to improper handling of user-supplied input in the `list_personalities` function, where the `category` parameter can be controlled to specify arbitrary directories for listing. Successful exploitation of this vulnerability could allow an attacker to list all folders in the drive on the system, potentially leading to information disclosure.

Weakness: CWE-29 (Path Traversal: '\..\filename')

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

It affects 1 product.


Products: Lollms Lollms Web Ui.

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

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

## Is CVE-2024-4322 being exploited?

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

Public exploit code:

- POC_CVE-2024-4322 (github_poc): https://github.com/MJ-bin/POC_CVE-2024-4322
- LoLLMS WebUI < 9.8 - Path Traversal (nuclei): http/cves/2024/CVE-2024-4322.yaml

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

What it is: CVE-2024-4322 is a high-severity path traversal vulnerability in parisneo/lollms-webui, published on 16 May 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-4322 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-4322/ (Markdown: https://insights.sbomify.com/CVE-2024-4322/index.md)
```

## Sources

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

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