Path Traversal in parisneo/lollms

The /setpersonalityconfig endpoint in lollms is vulnerable to path traversal, enabling attackers to manipulate file paths and access or modify files outside the intended directory. Specifically, an attacker can overwrite the configs/config.yaml file. This file contains crucial server configuration properties, including forceacceptremoteaccess and turnoncodevalidation. By modifying these settings, an attacker could disable security features, gain unauthorized remote access, or execute arbitrary code on the server. Successful exploitation could lead to a complete compromise of the lollms instance and potentially the underlying system.

Organizations and individuals deploying lollms, particularly those with publicly accessible instances or those lacking robust access controls, are at risk. Shared hosting environments where multiple users share the same lollms instance are also particularly vulnerable, as a compromised user could potentially impact other users on the same server.

• python / server:

import os
import requests

url = 'http://your-lollms-instance/set_personality_config' # Replace with your lollms instance

# Attempt path traversal
payload = "/../../../../etc/passwd"

# Send a request with the payload
response = requests.post(url, data={'personality_config': payload})

# Check the response status code
if response.status_code == 200:
    print("Potential Path Traversal Vulnerability Detected!")
else:
    print("No Path Traversal Detected.")

• generic web:

curl -I http://your-lollms-instance/set_personality_config/%2e%2e%2f%2e%2e%2fetc/passwd

• generic web:

grep -r 'force_accept_remote_access: true' /path/to/lollms/configs/config.yaml

1. 2024-06-27Disclosure

   disclosure

1. Reserviert2024-06-10
2. Veröffentlicht2024-06-27
3. Geändert2024-08-01
4. EPSS aktualisiert2026-04-02

The primary mitigation for CVE-2024-5824 is to upgrade to the latest version of lollms, which includes a fix for the path traversal vulnerability. If upgrading immediately is not feasible, consider implementing temporary workarounds. Restrict access to the /setpersonalityconfig endpoint to trusted users only. Implement strict input validation on the endpoint to prevent malicious path manipulation. Consider using a Web Application Firewall (WAF) to filter out requests containing path traversal attempts. Monitor system logs for suspicious file access or modification activity.