parisneo/lollms におけるパス・トラバーサル

The primary impact of CVE-2024-5824 is the potential for remote code execution. By exploiting the path traversal vulnerability, an attacker can overwrite the configs/config.yaml file. This file controls various server settings, including forceacceptremoteaccess and turnoncodevalidation. Modifying these settings could allow an attacker to bypass security controls, gain unauthorized access to the system, and execute arbitrary code. The blast radius extends to any data processed by the lollms instance, as an attacker could manipulate the model's behavior or steal sensitive information.

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. 予約済み2024-06-10
2. 公開日2024-06-27
3. 更新日2024-08-01
4. EPSS 更新日2026-04-02

The recommended mitigation for CVE-2024-5824 is to immediately upgrade to the latest version of lollms, which contains the fix. If upgrading is not immediately feasible, consider implementing a Web Application Firewall (WAF) rule to block requests targeting the /setpersonalityconfig endpoint with potentially malicious path traversal payloads. Additionally, restrict access to this endpoint to authorized users only. Monitor system logs for any unusual file modifications or access attempts to the configs/config.yaml file. After upgrading, confirm the fix by attempting to access the /setpersonalityconfig endpoint with a path traversal payload (e.g., /../../../../etc/passwd) and verifying that access is denied.