Service crash via forged ComfyUI installation request
Published Oct 29, 2024 · Updated Oct 29, 2024
CSRF in LoLLMs WebUI before 9.9 allows remote attackers to trigger a ComfyUI installation and crash the service through a victim's browser. The install_comfyui handler accepts a state-changing GET request without a client identifier, so cross-origin browser navigation starts the installer. Exploitation requires user interaction and browser access to the victim's local WebUI; the bounded consequence is unauthorized installation and a capacity-dependent crash.
Summary
What happened
CSRF in LoLLMs WebUI before 9.9 allows remote attackers to trigger a ComfyUI installation and crash the service through a victim's browser. The install_comfyui handler accepts a state-changing GET request without a client identifier, so cross-origin browser navigation starts the installer. Exploitation requires user interaction and browser access to the victim's local WebUI; the bounded consequence is unauthorized installation and a capacity-dependent crash.
The record
- CVE
- CVE-2024-6673
- Published
- Oct 29, 2024
- Updated
- Oct 29, 2024
- Vendor
- ParisNeo
- Product
- LoLLMs WebUI
- Classifications
- CWE-352, CAPEC-62, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 29, 2024CVE publishedPublication date reported by the CVE source.
- Oct 29, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <9.9
- Affected versionversion=unspecified <9.9
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Huntr CSRF proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo