DB-GPT vulnérable à une Téléchargement Arbitraire de Fichiers avec Traversal de Chemin

The primary impact of CVE-2024-10902 is the ability for an attacker to upload arbitrary files to the server. This is a severe risk because it can be leveraged for remote code execution (RCE). Specifically, the description highlights the possibility of writing a malicious init.py file into the Python /site-packages/ directory, which would execute upon import. This could grant the attacker complete control over the affected system. The path traversal aspect means the attacker isn't limited to a specific upload directory; they can choose any location on the file system, significantly expanding the potential damage. Successful exploitation could lead to data breaches, system compromise, and denial of service.

Organizations deploying eosphoros-ai/db-gpt in production environments, particularly those using it for sensitive data processing or AI-driven applications, are at significant risk. Environments with weak file upload validation or inadequate access controls are especially vulnerable. Shared hosting environments where multiple users share the same server resources are also at increased risk.

• python / server:

Get-ChildItem -Path "C:\\path\\to\\db-gpt\\uploads" -Recurse -Filter "*.py"

• generic web:

curl -I -X POST -F "file=@malicious_file.py" http://<target>/v1/personal/agent/upload | grep 'Location:'

1. 2025-03-20Disclosure

   disclosure

1. Réservé2024-11-05
2. Publiée2025-03-20
3. Modifiée2025-10-16
4. EPSS mis à jour2026-04-02

The primary mitigation for CVE-2024-10902 is to upgrade to a patched version of eosphoros-ai/db-gpt. Unfortunately, a fixed version is not specified in the provided data. As a temporary workaround, implement strict file upload validation on the POST /v1/personal/agent/upload endpoint. This should include whitelisting allowed file extensions and rigorously validating the file path to prevent traversal attempts. Consider using a Web Application Firewall (WAF) with rules to block suspicious file uploads and path manipulation attempts. Regularly scan the file system for unexpected or unauthorized files. After applying mitigations, verify the upload endpoint's security by attempting to upload a file with a deliberately malicious path.