CVE-2024-5482: Lollms Web UI SSRF Vulnerability

CVE-2024-5482 Overview

CVE-2024-5482 is a Server-Side Request Forgery (SSRF) vulnerability in the add_webpage endpoint of the parisneo/lollms-webui application. The application fails to validate user-supplied URLs, allowing attackers to submit arbitrary destinations including internal hosts like localhost and 127.0.0.1. Attackers can pivot through the application to reach internal services, exfiltrate sensitive data, disrupt backend systems, and abuse third-party resources. The flaw is classified under CWE-918 and affects the latest version of lollms-webui at the time of disclosure.

Critical Impact

Unauthenticated attackers can coerce the server into issuing arbitrary HTTP requests to internal infrastructure, exposing cloud metadata services, internal APIs, and non-public assets.

Affected Products

• parisneo/lollms-webui (latest version at time of disclosure)
• Deployments exposing the add_webpage endpoint to untrusted users
• Container and cloud installations of lollms-webui without egress filtering

Discovery Timeline

• 2024-06-06 - CVE-2024-5482 published to NVD
• 2024-11-21 - Last updated in NVD database

Technical Details for CVE-2024-5482

Vulnerability Analysis

The add_webpage endpoint accepts a URL parameter intended to ingest external web content into the lollms-webui knowledge pipeline. The handler issues a server-side HTTP request to the supplied URL without restricting the destination scheme, host, or IP range. Because the request originates from the server process, it inherits the host's network position and can reach resources that are otherwise unreachable from the public internet.

Attackers exploit this trust boundary to query loopback interfaces, RFC1918 ranges, link-local addresses such as 169.254.169.254, and internal DNS names. Cloud deployments are particularly exposed because metadata services frequently return temporary credentials to any HTTP client running on the instance.

Root Cause

The root cause is missing input validation on the URL parameter passed to add_webpage. The endpoint does not enforce an allowlist of permitted hosts, does not block private and loopback IP ranges, and does not restrict URL schemes to http and https against externally routable destinations. This maps directly to CWE-918: Server-Side Request Forgery.

Attack Vector

Exploitation requires only network access to the lollms-webui interface. An attacker submits a crafted URL to the add_webpage endpoint pointing at an internal target. The server resolves the host, opens a socket, and returns or processes the response, leaking content back to the attacker or triggering side effects on internal services. No authentication or user interaction is required. See the Huntr Bounty Report for the original disclosure.

Detection Methods for CVE-2024-5482

Indicators of Compromise

• Outbound HTTP requests from the lollms-webui process to loopback addresses, RFC1918 ranges, or cloud metadata endpoints such as 169.254.169.254
• Application logs showing add_webpage invocations with URLs containing internal hostnames, IP literals, or non-standard ports
• Unexpected access patterns in internal service logs originating from the lollms-webui host

Detection Strategies

• Inspect web server access logs for POST requests to /add_webpage containing URL parameters referencing internal targets
• Correlate process-level network telemetry from the lollms-webui container with the destination IP space to flag private-network egress
• Deploy egress monitoring to alert when the application initiates connections outside an approved allowlist of external content sources

Monitoring Recommendations

• Forward lollms-webui application logs and host network telemetry to a centralized analytics platform for retrospective hunting
• Alert on first-seen destinations from the lollms-webui service account, especially to metadata, loopback, or private addresses
• Track HTTP response sizes and status codes returned by the add_webpage handler to identify reconnaissance scans across internal ports

How to Mitigate CVE-2024-5482

Immediate Actions Required

• Restrict network access to the lollms-webui management interface so only trusted users can reach the add_webpage endpoint
• Place the lollms-webui host behind an egress proxy that denies traffic to loopback, link-local, and RFC1918 ranges
• Rotate any cloud instance credentials and API keys that may have been accessible via metadata services from the lollms-webui host

Patch Information

No vendor advisory or fixed-version reference is listed in the NVD record at the time of writing. Operators should monitor the parisneo/lollms-webui repository and the Huntr Bounty Report for remediation guidance and upgrade to a release that validates URLs submitted to add_webpage.

Workarounds

• Disable or remove the add_webpage functionality if it is not required by the deployment
• Front the application with a reverse proxy that strips or rewrites requests containing internal IP literals or disallowed schemes
• Run lollms-webui inside a network namespace or container with no route to internal management networks or cloud metadata endpoints

# Example: block egress to cloud metadata and private ranges from the lollms-webui container
iptables -A OUTPUT -d 169.254.169.254 -j REJECT
iptables -A OUTPUT -d 127.0.0.0/8 -j REJECT
iptables -A OUTPUT -d 10.0.0.0/8 -j REJECT
iptables -A OUTPUT -d 172.16.0.0/12 -j REJECT
iptables -A OUTPUT -d 192.168.0.0/16 -j REJECT