AstrBot Hat eine Path Traversal Schwachstelle in /api/chat/get_file

The primary impact of CVE-2025-48957 is information disclosure. An attacker can leverage the Path Traversal vulnerability to navigate outside the intended directory structure and access files they should not be able to view. This includes potentially exposing API keys used for Large Language Model (LLM) providers, account passwords, and other confidential data. Successful exploitation could lead to unauthorized access to services, data breaches, and compromise of user accounts. The ease of reproduction, as demonstrated by the provided steps, suggests a relatively low barrier to entry for attackers.

Organizations deploying AstrBot, particularly those using it to interact with LLM providers or storing sensitive credentials within the application's configuration files, are at significant risk. Shared hosting environments where AstrBot is installed alongside other applications are also vulnerable, as a compromised AstrBot instance could potentially be used to access files belonging to other tenants.

• python / server:

  # Check for AstrBot version
  python -c "import astrbot; print(astrbot.__version__)"

  # Monitor file access attempts in logs (if logging is enabled)
  grep -i "path traversal" /var/log/syslog

• generic web:

  # Attempt to access sensitive files via path traversal
  curl 'http://your-astrbot-server/../../../../etc/passwd'

1. 2025-06-04Disclosure

   disclosure

1. Reserviert2025-05-28
2. Veröffentlicht2025-06-04
3. Geändert2025-06-27
4. EPSS aktualisiert2026-03-23

The primary mitigation for CVE-2025-48957 is to upgrade AstrBot to version 3.5.13 or later. If an immediate upgrade is not possible due to compatibility issues or system downtime constraints, consider implementing temporary workarounds. While a direct WAF rule to prevent path traversal is difficult without understanding the application's intended file access patterns, restricting access to the AstrBot directory and its subdirectories through firewall rules can limit the potential attack surface. Regularly review and audit file permissions within the AstrBot installation directory to ensure only authorized users and processes have access. After upgrading, confirm the vulnerability is resolved by attempting to access files outside the intended directory structure and verifying that access is denied.