Skip to main content
Vulnerability Database/CVE-2024-10047

CVE-2024-10047: Lollms Web UI Path Traversal Vulnerability

CVE-2024-10047 is a path traversal vulnerability in Lollms Web UI that enables attackers to list arbitrary directories on Windows systems. This article covers the technical details, affected versions, exploitation risks, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2024-10047 Overview

CVE-2024-10047 is a directory listing vulnerability affecting parisneo/lollms-webui versions v9.9 through the latest release. An unauthenticated attacker can enumerate arbitrary directories on a Windows host by sending a crafted HTTP request to the /open_file endpoint. The flaw is categorized under [CWE-36: Absolute Path Traversal] and allows remote information disclosure without user interaction or privileges. The issue is specific to Windows deployments of the Lollms Web UI, a popular open-source interface for local large language model workflows.

Critical Impact

Remote attackers can enumerate arbitrary directory contents on Windows systems running lollms-webui without authentication, exposing file structure and potentially sensitive filenames.

Affected Products

  • parisneo lollms-webui version 9.9
  • parisneo lollms-webui versions after 9.9 up to the latest release at time of disclosure
  • Windows-based deployments of lollms-webui

Discovery Timeline

  • 2025-03-20 - CVE-2024-10047 published to the National Vulnerability Database (NVD)
  • 2026-06-17 - Last updated in NVD database

Technical Details for CVE-2024-10047

Vulnerability Analysis

The vulnerability resides in the /open_file HTTP endpoint exposed by the lollms-webui application. The endpoint accepts a file path parameter from the client and processes it without sufficient validation of the target location. On Windows installations, an attacker can submit an absolute path to any directory on the host and receive a listing of its contents in the HTTP response.

Because the endpoint does not require authentication, any party with network access to the lollms-webui service can issue the request. The exposed information includes file names, subdirectory names, and structural layout of the targeted path. Attackers can use this data to map user profiles, locate configuration files, identify installed software, and plan follow-up attacks against higher-value targets.

The weakness is classified as [CWE-36: Absolute Path Traversal], a subclass of path traversal where the attacker supplies a fully qualified path rather than relative traversal sequences. See the Huntr Bug Bounty Submission for additional technical context.

Root Cause

The /open_file endpoint trusts user-supplied path input and performs no allowlist validation, canonicalization, or restriction to an application-controlled base directory. The handler executes a Windows directory enumeration routine against the attacker-controlled path and returns the result to the caller.

Attack Vector

Exploitation requires only network reachability to the lollms-webui HTTP service. An attacker sends a single HTTP request to /open_file referencing an absolute Windows path such as a user profile directory, C:\\Users\\, or a program data location. The server responds with the directory listing. No credentials, cookies, or prior interaction are needed, and the request pattern is indistinguishable from legitimate feature use at the network layer.

Detection Methods for CVE-2024-10047

Indicators of Compromise

  • HTTP requests to the /open_file endpoint containing absolute Windows paths such as C:\\, D:\\, or UNC paths in request parameters
  • Repeated /open_file requests from the same remote source enumerating multiple directories in a short interval
  • Access to the /open_file endpoint from source addresses outside the expected administrative scope

Detection Strategies

  • Review web server and reverse proxy access logs for unauthenticated calls to /open_file with path parameters referencing system directories
  • Alert on /open_file requests originating from external or unexpected network segments
  • Correlate /open_file activity with subsequent requests targeting discovered file paths to identify reconnaissance-to-exploitation sequences

Monitoring Recommendations

  • Enable verbose HTTP request logging on the lollms-webui host and forward logs to a central analytics platform
  • Monitor for process-level file enumeration activity by the Python runtime hosting lollms-webui outside expected working directories
  • Baseline normal /open_file usage patterns and alert on deviations in request volume or path scope

How to Mitigate CVE-2024-10047

Immediate Actions Required

  • Restrict network access to the lollms-webui service so it is reachable only from trusted administrative hosts
  • Place the application behind an authenticated reverse proxy that requires login before any request reaches the backend
  • Block external requests to the /open_file endpoint at the proxy or web application firewall layer
  • Audit historical access logs for prior exploitation attempts referencing absolute paths

Patch Information

No vendor patch is referenced in the NVD entry for CVE-2024-10047 at the time of writing. Monitor the parisneo/lollms-webui project for a fixed release and review the Huntr Bug Bounty Submission for remediation status. Upgrade to the latest release once the maintainers publish a version that validates input to /open_file.

Workarounds

  • Bind the lollms-webui listener to 127.0.0.1 so the service is unreachable from the network
  • Deploy a reverse proxy with an allowlist that rejects requests to /open_file from untrusted sources
  • Run lollms-webui under a low-privilege Windows account that lacks read access to sensitive directories
  • Deploy on Linux where available, since the reported vulnerability is specific to Windows directory enumeration behavior
bash
# Example nginx rule to block external access to /open_file
location /open_file {
    allow 127.0.0.1;
    allow 10.0.0.0/8;
    deny all;
    proxy_pass http://127.0.0.1:9600;
}

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.