MariaDB mariadb-dump Dienst Verzeichnisübergreifende Ausführung von Remote-Code-Vulnerabilität. Diese Schwachstelle ermöglicht es Remote-Angreifern, beliebigen Code auf betroffenen Installationen von MariaDB auszuführen. Die Interaktion mit der Dienstprogramm-Funktion mariadb-dump ist erforderlich, um diese Schwachstelle auszunutzen, aber die Angriffsvektoren können je nach Implementierung variieren. Der spezifische Fehler liegt in der Behandlung von View-Namen. Das Problem ergibt sich aus dem Fehlen einer ordnungsgemäßen Validierung eines vom Benutzer bereitgestellten Pfads vor der Verwendung in fil

The impact of CVE-2025-13699 is significant, as successful exploitation grants an attacker the ability to execute arbitrary code on the MariaDB server. This could lead to complete system compromise, including data exfiltration, modification, or deletion. Attackers could leverage this vulnerability to gain persistent access, install malware, or pivot to other systems within the network. The requirement for interaction with mariadb-dump might necessitate social engineering or exploiting other vulnerabilities to trigger the code execution, but the potential blast radius is substantial, potentially impacting the entire database infrastructure and any applications relying on it.

Organizations utilizing MariaDB in environments where the mariadb-dump utility is exposed or used with untrusted input are at risk. This includes development and testing environments, as well as production systems with custom scripts or applications that interact with the database using mariadb-dump. Shared hosting environments where multiple users share the same MariaDB instance are particularly vulnerable.

• mariadb / server:

journalctl -u mariadb | grep -i "view name"

• mariadb / server:

ps aux | grep mariadb-dump

• generic web: Check for unusual file access attempts in MariaDB error logs related to view names. • mariadb / server: Examine MariaDB configuration files for any unusual or insecure settings related to the mariadb-dump utility.

1. 2025-12-23Disclosure

   disclosure

1. Reserviert2025-11-25
2. Veröffentlicht2025-12-23
3. Geändert2025-12-29
4. EPSS aktualisiert2026-03-23

Due to the absence of a specific fixed_in version, immediate mitigation strategies are crucial. Restricting direct access to the mariadb-dump utility is the primary defense. Implement strict file access controls, ensuring that the utility can only be executed by authorized users and processes. Monitor system logs for any suspicious activity related to mariadb-dump, particularly unusual file access patterns or command-line arguments. Consider using a Web Application Firewall (WAF) or proxy to filter requests to the MariaDB server and block potentially malicious input. After implementing these controls, verify their effectiveness by attempting to trigger the vulnerability in a controlled environment.