Remote Code Execution due to LFI in '/install_extension' in parisneo/lollms-webui

The impact of CVE-2024-4320 is severe. An attacker can exploit this vulnerability to execute arbitrary code within the context of the lollms-webui application, potentially gaining full control of the underlying server. This could lead to data breaches, system compromise, and further malicious activity. The ability to load and execute arbitrary Python code via LFI significantly expands the attack surface, allowing attackers to install malware, steal sensitive data, or disrupt services. The vulnerability’s location within an extension installation process makes it particularly concerning, as attackers could potentially inject malicious extensions to achieve persistent access.

Organizations deploying lollms-webui, particularly those running it in production environments or on systems containing sensitive data, are at significant risk. Shared hosting environments where multiple users share the same server are also particularly vulnerable, as a compromise of one user's installation could potentially impact others.

• linux / server:

journalctl -u lollms-webui -g 'install_extension' | grep -i 'file: ' # Look for suspicious file paths

• generic web:

curl -I http://your-lollms-webui/install_extension?name=../../../../etc/passwd # Attempt LFI

• python / supply-chain: Inspect the ExtensionBuilder().build_extension() method in the lollms-webui source code for improper input validation.

1. 2024-06-06Disclosure

   disclosure

1. Gereserveerd2024-04-29
2. Gepubliceerd2024-06-06
3. Gewijzigd2024-08-01
4. EPSS bijgewerkt2026-04-02

The primary mitigation for CVE-2024-4320 is to immediately upgrade to a patched version of lollms-webui. Since a fixed version is not yet available, a temporary workaround involves disabling the /install_extension endpoint or implementing strict input validation on the name parameter to prevent the inclusion of arbitrary files. Consider using a Web Application Firewall (WAF) to filter requests containing suspicious filenames or paths. Monitor system logs for unusual file access patterns or attempts to execute Python code from unexpected locations. After applying any mitigation, verify its effectiveness by attempting to trigger the vulnerability with a benign payload and confirming that it is blocked.