rConfig vulnerabilities

rConfig 3.9.6 is affected by a Local File Disclosure vulnerability. An authenticated user may successfully download any file on the server.

rConfig before 8.2.13 has a path traversal vulnerability in the download_export() method, allowing authenticated attackers to read arbitrary files by supplying ../ sequences in the filename parameter. Sensitive files like environment files with encryption keys, database credentials, and mail config can be accessed.

rconfig v3.9.4 was discovered to contain a Server-Side Request Forgery (SSRF) via the path parameter at /ajaxGetFileByPath.php. This vulnerability allows authenticated attackers to make arbitrary requests via injection of crafted URLs.

rconfig v3.9.4 was discovered to contain a Server-Side Request Forgery (SSRF) via the path_a parameter in the doDiff Function of /classes/compareClass.php. This vulnerability allows authenticated attackers to make arbitrary requests via injection of crafted URLs.

In version 3.9.4 of rconfig, a Server-Side Request Forgery (SSRF) vulnerability was discovered in the path_b parameter of the doDiff function in /classes/compareClass.php. This allows authenticated attackers to make arbitrary requests by injecting crafted URLs.

In rConfig 3.9.6, insecure permissions for the chmod command exist. After installation, the apache user can execute chmod as root without a password, allowing a low-privilege attacker to gain root access to the server.

SQL Injection vulnerability in rConfig 3.9.6 allows an authenticated attacker to inject malicious SQL code. If the MySQL server does not have --secure-file-priv set and is on the same host as rConfig, the attacker can upload a webshell and gain remote access.