Vulnerabilities > Bestpractical > RT > 3.1.4
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2012-06-04 | CVE-2011-5092 | Permissions, Privileges, and Access Controls vulnerability in Bestpractical RT Best Practical Solutions RT 3.8.x before 3.8.12 and 4.x before 4.0.6 allows remote attackers to execute arbitrary code and gain privileges via unspecified vectors, a different vulnerability than CVE-2011-4458 and CVE-2011-5093. | 7.5 |
| 2012-06-04 | CVE-2011-4460 | SQL Injection vulnerability in Bestpractical RT SQL injection vulnerability in Best Practical Solutions RT 2.x and 3.x before 3.8.12 and 4.x before 4.0.6 allows remote authenticated users to execute arbitrary SQL commands by leveraging access to a privileged account. | 6.5 |
| 2012-06-04 | CVE-2011-4459 | Permissions, Privileges, and Access Controls vulnerability in Bestpractical RT Best Practical Solutions RT 3.x before 3.8.12 and 4.x before 4.0.6 does not properly disable groups, which allows remote authenticated users to bypass intended access restrictions in opportunistic circumstances by leveraging a group membership. | 3.5 |
| 2012-06-04 | CVE-2011-2084 | Information Exposure vulnerability in Bestpractical RT Best Practical Solutions RT 3.x before 3.8.12 and 4.x before 4.0.6 allows remote authenticated users to read (1) hashes of former passwords and (2) ticket correspondence history by leveraging access to a privileged account. | 4.0 |
| 2012-06-04 | CVE-2011-2083 | Cross-Site Scripting vulnerability in Bestpractical RT Multiple cross-site scripting (XSS) vulnerabilities in Best Practical Solutions RT 3.x before 3.8.12 and 4.x before 4.0.6 allow remote attackers to inject arbitrary web script or HTML via unspecified vectors. | 4.3 |
| 2012-06-04 | CVE-2011-2082 | Credentials Management vulnerability in Bestpractical RT The vulnerable-passwords script in Best Practical Solutions RT 3.x before 3.8.12 and 4.x before 4.0.6 does not update the password-hash algorithm for disabled user accounts, which makes it easier for context-dependent attackers to determine cleartext passwords, and possibly use these passwords after accounts are re-enabled, via a brute-force attack on the database. | 5.0 |