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

> Attackers can traverse directories to view folder names via the list_personalities endpoint in lollms-webui.

- **Severity:** Medium 4.0 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 May 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-9p73-x86v-jw57, PYSEC-2026-1589

## What is CVE-2024-4330?

CVE-2024-4330 is a medium-severity path traversal vulnerability in parisneo/lollms-webui, published on 30 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A path traversal vulnerability was identified in the parisneo/lollms-webui repository, specifically within version 9.6. The vulnerability arises due to improper handling of user-supplied input in the 'list_personalities' endpoint. By crafting a malicious HTTP request, an attacker can traverse the directory structure and view the contents of any folder, albeit limited to subfolder names only. This issue was demonstrated via a specific HTTP request that manipulated the 'category' parameter to access arbitrary directories. The vulnerability is present in the code located at the 'endpoints/lollms_advanced.py' file.

Weakness: CWE-23 (Relative Path Traversal)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `lollms` | PyPI | All versions | None |
| `lollms` | PyPI | All versions | None |
| `lollms` | PyPI | All versions | None |

Products: Lollms Lollms Web Ui.

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

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

## Is CVE-2024-4330 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-4330 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-4330 and fix it if it is affected.

What it is: CVE-2024-4330 is a medium-severity path traversal vulnerability in parisneo/lollms-webui, published on 30 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-4330 exists.

Affected packages and fixed versions:
- lollms (PyPI): affected all versions; no fix listed
- lollms (PyPI): affected all versions; no fix listed
- lollms (PyPI): affected all versions; 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-4330/ (Markdown: https://insights.sbomify.com/CVE-2024-4330/index.md)
```

## Sources

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

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