Business Logic Errors in GitHub repository froxlor/froxlor prior to 2.0.10.

froxlor

Weak Password Requirements in GitHub repository froxlor/froxlor prior to 2.0.10.

froxlor

Path Traversal: '\..\filename' in GitHub repository froxlor/froxlor prior to 2.0.0.

froxlor

Command Injection in GitHub repository froxlor/froxlor prior to 2.0.8.

froxlor

Improper Authorization in GitHub repository froxlor/froxlor prior to 2.0.0-beta1.

froxlor

Cross-Site Request Forgery (CSRF) in GitHub repository froxlor/froxlor prior to 2.0.0-beta1.

froxlor

Argument Injection in GitHub repository froxlor/froxlor prior to 2.0.0-beta1.

froxlor

Code Injection in GitHub repository froxlor/froxlor prior to 0.10.38.2.

froxlor

Code Injection in GitHub repository froxlor/froxlor prior to 0.10.39.

froxlor

Cross-Site Request Forgery (CSRF) in GitHub repository froxlor/froxlor prior to 0.10.38.

froxlor

Froxlor through 0.10.22 does not perform validation on user input passed in the customermail GET parameter. The value of this parameter is reflected in the login webpage, allowing the injection of arbitrary HTML tags.

froxlor

Froxlor through 0.10.29.1 allows SQL injection in Database/Manager/DbManagerMySQL.php via a custom DB name.

froxlor

An issue was discovered in Froxlor through 0.10.15. The installer wrote configuration parameters including passwords into files in /tmp, setting proper permissions only after writing the sensitive data. A local attacker could have disclosed the information if he read the file at the right time, because of _createUserdataConf in install/lib/class.FroxlorInstall.php.

froxlor

An issue was discovered in Froxlor before 0.10.14. It created files with static names in /tmp during installation if the installation directory was not writable. This allowed local attackers to cause DoS or disclose information out of the config files, because of _createUserdataConf in install/lib/class.FroxlorInstall.php.

froxlor

An issue was discovered in Froxlor before 0.10.14. Remote attackers with access to the installation routine could have executed arbitrary code via the database configuration options that were passed unescaped to exec, because of _backupExistingDatabase in install/lib/class.FroxlorInstall.php.

froxlor

Froxlor version <= 0.9.39.5 contains a PHP Object Injection vulnerability in Domain name form that can result in Possible information disclosure and remote code execution. This attack appear to be exploitable via Passing malicious PHP objection in $_POST['ssl_ipandport']. This vulnerability appears to have been fixed in after commit c1e62e6.

froxlor

Froxlor through 0.9.39.5 has Incorrect Access Control for tickets not owned by the current user.

froxlor

Froxlor before 0.9.33.2 with the default configuration/setup might allow remote attackers to obtain the database password by reading /logs/sql-error.log.

froxlor

Froxlor before 0.9.35 uses the PHP rand function for random number generation, which makes it easier for remote attackers to guess the password reset token by predicting a value.

froxlor

frox 0.7.16 and 0.7.17 does not properly parse certain Deny ACLs, which might allow attackers to bypass intended restrictions and access blocked hosts.

frox

frox 0.7.18, when running setuid root, does not properly drop privileges when reading a configuration file, which allows local users to read portions of arbitrary files via the -f command line option.

frox