Path Traversal leading to Arbitrary File Write and RCE in vertaai/modeldb

The primary impact of CVE-2024-1961 is Remote Code Execution. An attacker can leverage this vulnerability to upload and write files to arbitrary locations on the server's filesystem. This is achieved by manipulating the 'artifact_path' parameter during file uploads, bypassing intended security controls. The most critical scenario involves overwriting the application's configuration file, potentially injecting malicious code that executes upon application startup. This could grant the attacker persistent access and control over the system. Because the vulnerability is tied to file system access, it could also be used to exfiltrate sensitive data stored on the server, depending on file permissions. The risk is amplified when vertaai/modeldb is deployed outside of Docker containers, as it lacks the isolation provided by containerization.

Organizations deploying vertaai/modeldb outside of Docker containers are at the highest risk. Environments with weak file access controls or inadequate input validation are also particularly vulnerable. Development environments and testing systems running vertaai/modeldb should be prioritized for patching.

• python / server:

find / -name 'NFSController.java' -o -name 'NFSService.java' 2>/dev/null

• python / server:

ps aux | grep -i modeldb

• generic web: Inspect file upload endpoints for the presence of the 'artifact_path' parameter. Monitor access logs for requests containing unusual or absolute file paths.

1. 2024-04-16Disclosure

   disclosure

1. Reserviert2024-02-27
2. Veröffentlicht2024-04-16
3. Geändert2024-08-29
4. EPSS aktualisiert2026-04-02

The immediate mitigation for CVE-2024-1961 is to upgrade to the patched version of vertaai/modeldb as soon as it becomes available. Until the patch is applied, consider implementing stricter file upload validation and sanitization on the server-side. Restrict write permissions on the application's deployment directory to the minimum necessary. Employ a Web Application Firewall (WAF) with rules to detect and block attempts to manipulate file paths, specifically targeting the 'artifact_path' parameter. Monitor application logs for suspicious file upload activity and unusual file modifications.