Multiple vulnerabilities have been reported in RT, which can be exploited by malicious users to disclose potentially sensitive information, conduct SQL injection attacks, and bypass certain security restrictions and by malicious people to conduct cross-site scripting attacks, cross-site request forgery attacks, and compromise a vulnerable system. 1) An error within the handling of tickets can be exploited by disclose certain information. This is related to: SA43438 2) Certain unspecified input is not properly sanitised before being returned to the user. This can be exploited to execute arbitrary HTML and script code in a user's browser session in context of an affected site. 3) An unspecified error can be exploited to disclose the correspondence history of a ticket. 4) The application allows users to perform certain actions via HTTP requests without performing any validity checks to verify the requests. This can be exploited to perform certain unspecified actions by tricking a logged in administrator into visiting a malicious web site. 5) An unspecified error can be exploited to execute arbitrary code. Successful exploitation of this vulnerability requires that the VERP configuration options are enabled. 6) An error within the handling of access rights may lead to certain users in disabled groups gaining additional privileges. 7) Certain unspecified input is not properly sanitised before being used in SQL queries. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code. The vulnerabilities are reported in versions prior to 3.8.12 and 4.0.6. Reproducible: Always
From secunia security advisory at $URL
www-apps/rt conduct SQL injection attacks, and bypass certain security restrictions and by malicious people to conduct cross-site scripting attacks, cross-site request forgery attacks, and compromise a vulnerable system. CVE-2011-2082
CVE-2011-5093 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-5093): Best Practical Solutions RT 4.x before 4.0.6 does not properly implement the DisallowExecuteCode option, which allows remote authenticated users to bypass intended access restrictions and execute arbitrary code by leveraging access to a privileged account, a different vulnerability than CVE-2011-4458 and CVE-2011-5092. CVE-2011-5092 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-5092): 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. CVE-2011-4460 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-4460): 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. CVE-2011-4459 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-4459): 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. CVE-2011-4458 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-4458): Best Practical Solutions RT 3.6.x, 3.7.x, and 3.8.x before 3.8.12 and 4.x before 4.0.6, when the VERPPrefix and VERPDomain options are enabled, allows remote attackers to execute arbitrary code via unspecified vectors, a different vulnerability than CVE-2011-5092 and CVE-2011-5093. CVE-2011-2085 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-2085): Multiple cross-site request forgery (CSRF) vulnerabilities in Best Practical Solutions RT before 3.8.12 and 4.x before 4.0.6 allow remote attackers to hijack the authentication of arbitrary users. CVE-2011-2084 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-2084): 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. CVE-2011-2083 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-2083): 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. CVE-2011-2082 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-2082): 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. NOTE: this vulnerability exists because of an incomplete fix for CVE-2011-0009.
*** Bug 440770 has been marked as a duplicate of this bug. ***
CVE-2012-4884 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2012-4884): Argument injection vulnerability in Request Tracker (RT) 3.8.x before 3.8.15 and 4.0.x before 4.0.8 allows remote attackers to create arbitrary files via unspecified vectors related to the GnuPG client. CVE-2012-4734 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2012-4734): Request Tracker (RT) 3.8.x before 3.8.15 and 4.0.x before 4.0.8 allows remote attackers to conduct a "confused deputy" attack to bypass the CSRF warning protection mechanism and cause victims to "modify arbitrary state" via unknown vectors related to a crafted link. CVE-2012-4732 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2012-4732): Cross-site request forgery (CSRF) vulnerability in Request Tracker (RT) 3.8.12 and other versions before 3.8.15, and 4.0.6 and other versions before 4.0.8, allows remote attackers to hijack the authentication of users for requests that toggle ticket bookmarks. CVE-2012-4730 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2012-4730): Request Tracker (RT) 3.8.x before 3.8.15 and 4.0.x before 4.0.8 allows remote authenticated users with ModifySelf or AdminUser privileges to inject arbitrary email headers and conduct phishing attacks or obtain sensitive information via unknown vectors.
I just tested rt-3.8.15 and rt-4.0.8 locally. They only require a copy of the ebuild. Both address the above security issues. Shall I go ahead and bump?
(In reply to comment #6) > I just tested rt-3.8.15 and rt-4.0.8 locally. They only require a copy of > the ebuild. Both address the above security issues. > > Shall I go ahead and bump? Okay I bumped. Six months on a security bug is long so sorry if I stepped on toes.
thanks, fixed
