Skip to main content

CVE-2024-6673: Lollms Web UI CSRF Vulnerability

CVE-2024-6673 is a Cross-Site Request Forgery vulnerability in Lollms Web UI that enables attackers to trick users into installing ComfyUI without authorization, potentially causing system crashes. This article covers technical details, affected versions, security impact, 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-6673 Overview

CVE-2024-6673 is a Cross-Site Request Forgery (CSRF) vulnerability [CWE-352] in the install_comfyui endpoint of lollms_comfyui.py in the parisneo/lollms-webui repository. The affected endpoint accepts GET requests without requiring a client ID or anti-CSRF token. An attacker can craft a malicious page that triggers the victim's browser to initiate a ComfyUI installation on the local lollms-webui instance. If the victim's device lacks sufficient disk or memory capacity to complete the installation, the process can crash the host application. The flaw affects lollms-webui versions v9.9 through the latest release at time of disclosure.

Critical Impact

Remote attackers can force unattended installation of ComfyUI on a victim's lollms-webui instance, leading to resource exhaustion and application crash.

Affected Products

  • parisneo lollms-webui v9.9 through latest at disclosure
  • lollms_comfyui.py module
  • Deployments exposing the lollms-webui HTTP interface to untrusted browsers

Discovery Timeline

  • 2024-10-29 - CVE-2024-6673 published to NVD
  • 2026-06-17 - Last updated in NVD database

Technical Details for CVE-2024-6673

Vulnerability Analysis

The install_comfyui endpoint in lollms_comfyui.py performs a state-changing operation (installing ComfyUI) in response to an HTTP GET request. The endpoint does not validate the origin of the request, does not require a CSRF token, and does not bind the request to a client ID. Any authenticated user visiting an attacker-controlled page can be forced to initiate the installation without consent.

The installation process downloads and provisions ComfyUI resources on the host running lollms-webui. On systems with constrained storage, memory, or CPU, this provisioning step can exhaust available resources and crash the lollms-webui process, producing a denial-of-service condition.

Root Cause

The root cause is missing CSRF protection on a resource-intensive, state-changing endpoint. Two design decisions compound the issue: use of GET for an installation action, and the absence of a per-session client ID or token requirement. Both violate accepted web application security practice for state-changing requests.

Attack Vector

Exploitation requires user interaction. An attacker hosts a page containing an <img>, <iframe>, or fetch() call targeting the victim's local lollms-webui URL and the vulnerable path. When the victim visits the page, the browser issues the GET request against the local instance and triggers installation. No credentials beyond the victim's existing session are required.

For technical details and proof-of-concept information, see the Huntr bounty listing.

Detection Methods for CVE-2024-6673

Indicators of Compromise

  • Unexpected GET requests to /install_comfyui or related lollms_comfyui paths in web server access logs
  • Cross-origin Referer or Origin headers on requests targeting the install endpoint
  • Sudden disk-space consumption on hosts running lollms-webui, coinciding with ComfyUI directories being created
  • Unexpected lollms-webui process crashes or out-of-memory kernel messages following web traffic

Detection Strategies

  • Alert on HTTP GET requests to the install_comfyui path originating from external referrers
  • Baseline normal install activity for lollms-webui and flag deviations outside maintenance windows
  • Correlate web access logs with host-level resource metrics to identify installation-triggered exhaustion

Monitoring Recommendations

  • Monitor filesystem growth under directories where ComfyUI is provisioned
  • Track lollms-webui process uptime and restart counts to detect crash-restart loops
  • Capture and review HTTP Referer and Origin headers for all state-changing endpoints

How to Mitigate CVE-2024-6673

Immediate Actions Required

  • Upgrade lollms-webui to the version containing commit c1bb1ad or later
  • Restrict network exposure of lollms-webui to trusted hosts only, using a reverse proxy or firewall
  • Require authentication on the web UI and avoid shared browser sessions during administrative work

Patch Information

The maintainers published a fix in the parisneo/lollms-webui repository. The referenced commit updates the built web assets, as reflected in web/dist/index.html:

text
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
     <title>LoLLMS WebUI - Welcome</title>
-    <script type="module" crossorigin src="/assets/index-746e673b.js"></script>
-    <link rel="stylesheet" href="/assets/index-28b1b09c.css">
+    <script type="module" crossorigin src="/assets/index-635d7a9c.js"></script>
+    <link rel="stylesheet" href="/assets/index-e245928f.css">
   </head>
   <body>
     <div id="app"></div>

Source: parisneo/lollms-webui commit c1bb1ad.

Workarounds

  • Block external access to install endpoints at the reverse proxy, allowing only localhost or administrative IP ranges
  • Enforce SameSite=Strict cookies on the lollms-webui session to limit cross-site request delivery
  • Add origin validation at a fronting proxy for requests to lollms-webui state-changing paths
  • Log out of lollms-webui when browsing untrusted sites to reduce the exposure window
bash
# Example nginx snippet restricting the vulnerable path to internal clients
location ~ ^/install_comfyui {
    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.