REDHAT-BUG-696795: SQL Injection

Published Apr 14, 2011
·
Updated

Several flaws have been reported [1] and corrected in RT versions 3.6.11 and 3.8.10, including:

RT versions 3.8.0 and above with the "external custom field" feature enabled and configured are vulnerable to a remote code execution vulnerability. An authenticated user (either privileged orunprivileged) can use this vulnerability to execute arbitrary code with the permissions of the webserver; they may also be tricked into doing so via cross-site request forgery (CSRF). (CVE-2011-1685)

RT versions 2.0.0 and above are vulnerable to multiple SQL injection attacks. We do not believe these attacks to be capable of directly inserting, altering or removing data from the database, but an authenticated user (either privileged or unprivileged) could use them to retrieve unauthorized ticket data. (CVE-2011-1686)

RT versions 3.0.0 and higher are vulnerable to an information leak wherein an authenticated privileged user could gain sensitive information, such as encrypted passwords, via the search interface. (CVE-2011-1687)

RT versions 3.6.0 through 3.8.7, as well as 3.8.8 to a more limited degree, are vulnerable to a malicious attacker tricking the user into sending their authentication credentials to a third-party server. (CVE-2011-1690)

RT versions 3.2.0 and above are vulnerable to a directory traversal attack where an unauthenticated attacker can read any file which is readable by the webserver. While some servers (Apache, nginx) have safeguards which mitigate this attack, preventing such traversals from accessing files outside of RT's document root, many others (including the standalone server provided with RT, plackup, starman, twiggy, and lighttpd) are vulnerable to this exploit. (CVE-2011-1688)

RT versions 2.0.0 and above are vulnerable to javascript cross-site-scripting vulnerabilities, which allow an attacker to run javascript with the user's credentials. (CVE-2011-1689)

Upstream have released a patchset [2] as well for 3.6.10 and 3.8 releases, in addition to the new releases.

[1] http://blog.bestpractical.com/2011/04/security-vulnerabilities-in-rt.html [2] http://download.bestpractical.com/pub/rt/release/security-2011-04-14.tar.gz

Affected Software

4 affected components
Best Practical Solutions RT>=3.8.0
Best Practical Solutions RT>=2.0.0
Best Practical Solutions RT>=3.0.0
Best Practical Solutions RT>=3.6.11<=3.8.10

Event History

Apr 14, 2011
Data Sourced
via Red Hat·08:33 PM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of REDHAT-BUG-696795?

The vulnerability REDHAT-BUG-696795 is considered critical due to the potential for remote code execution.

2

How do I fix REDHAT-BUG-696795?

To fix REDHAT-BUG-696795, upgrade RT to versions 3.6.11 or 3.8.10 and later where the flaw has been patched.

3

Who is affected by REDHAT-BUG-696795?

All users of RT versions 3.8.0 and above with the external custom field feature enabled are affected by REDHAT-BUG-696795.

4

What type of vulnerability is REDHAT-BUG-696795?

REDHAT-BUG-696795 is a remote code execution vulnerability that can be triggered by authenticated users.

5

Is REDHAT-BUG-696795 present in earlier versions of RT?

Yes, REDHAT-BUG-696795 affects RT versions from 3.0.0 and above up to 3.8.10, as well as version 2.0.0.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203