SSRF - file:// unsanitized access to underlying host files

The SSRF vulnerability in anything-llm allows an attacker to bypass security controls and make requests to internal resources that are otherwise inaccessible. By crafting a malicious POST request containing a file:// URL, an attacker can potentially read arbitrary files on the server's file system. This includes configuration files, sensitive data, and potentially even source code. The impact is particularly severe if the application is running with elevated privileges, as the attacker could then access files owned by the application's user. This could lead to complete compromise of the server and its data.

Applications utilizing the anything-llm Node.js library in versions prior to 1.0.0 are at risk. This includes applications that process user-supplied URLs without proper validation, particularly those deployed in environments where file system access is not strictly controlled. Shared hosting environments where the application has access to the host's file system are particularly vulnerable.

• nodejs / server:

  npm list anything-llm | grep -q '1.0.0' || echo "Vulnerable version detected!" 

• generic web:

  curl -I 'http://your-server/your-endpoint?url=file:///etc/passwd' | grep 'HTTP/1.1 403' # Check for access denied

1. 2024-02-25Disclosure

   disclosure

1. Reserviert2024-01-11
2. Veröffentlicht2024-02-25
3. Geändert2024-08-28
4. EPSS aktualisiert2026-04-02

The primary mitigation for CVE-2024-0440 is to upgrade to version 1.0.0 or later of the anything-llm library. If upgrading is not immediately feasible, consider implementing input validation on the link submission endpoint to prevent the use of the file:// protocol. Additionally, restrict the permissions of the application user to minimize the potential impact of a successful attack. Web application firewalls (WAFs) can be configured to block requests containing the file:// protocol. Monitor application logs for suspicious requests containing file paths.