low
2.1
CWE
255
Advisory Published
Updated

CVE-2011-1007

First published: Mon Feb 28 2011(Updated: )

Best Practical Solutions RT before 3.8.9 does not perform certain redirect actions upon a login, which allows physically proximate attackers to obtain credentials by resubmitting the login form via the back button of a web browser on an unattended workstation after an RT logout.

Credit: secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
Best Practical Solutions Request Tracker<=3.8.9
Best Practical Solutions Request Tracker=3.0.4
Best Practical Solutions Request Tracker=2.0.7
Best Practical Solutions Request Tracker=3.8.9-rc2
Best Practical Solutions Request Tracker=3.0.8
Best Practical Solutions Request Tracker=3.8.8-rc2
Best Practical Solutions Request Tracker=3.8.9-rc1
Best Practical Solutions Request Tracker=2.0.6
Best Practical Solutions Request Tracker=3.4.5
Best Practical Solutions Request Tracker=3.0.2
Best Practical Solutions Request Tracker=2.0.14
Best Practical Solutions Request Tracker=3.6.7
Best Practical Solutions Request Tracker=3.6.2
Best Practical Solutions Request Tracker=3.2.2
Best Practical Solutions Request Tracker=3.6.3
Best Practical Solutions Request Tracker=3.0.11
Best Practical Solutions Request Tracker=3.8.2
Best Practical Solutions Request Tracker=3.8.8-rc4
Best Practical Solutions Request Tracker=2.0.15
Best Practical Solutions Request Tracker=3.6.0
Best Practical Solutions Request Tracker=2.0.5.3
Best Practical Solutions Request Tracker=1.0.7
Best Practical Solutions Request Tracker=1.0.1
Best Practical Solutions Request Tracker=3.8.0
Best Practical Solutions Request Tracker=3.4.0
Best Practical Solutions Request Tracker=1.0.5
Best Practical Solutions Request Tracker=2.0.8.2
Best Practical Solutions Request Tracker=2.0.13
Best Practical Solutions Request Tracker=3.0.10
Best Practical Solutions Request Tracker=3.8.8-rc3
Best Practical Solutions Request Tracker=2.0.11
Best Practical Solutions Request Tracker=2.0.0
Best Practical Solutions Request Tracker=2.0.1
Best Practical Solutions Request Tracker=3.2.3
Best Practical Solutions Request Tracker=2.0.2
Best Practical Solutions Request Tracker=3.0.5
Best Practical Solutions Request Tracker=3.2.0
Best Practical Solutions Request Tracker=3.0.0
Best Practical Solutions Request Tracker=3.4.6
Best Practical Solutions Request Tracker=3.0.3
Best Practical Solutions Request Tracker=3.4.3
Best Practical Solutions Request Tracker=2.0.8
Best Practical Solutions Request Tracker=3.6.9
Best Practical Solutions Request Tracker=3.6.6
Best Practical Solutions Request Tracker=2.0.5
Best Practical Solutions Request Tracker=3.6.5
Best Practical Solutions Request Tracker=1.0.2
Best Practical Solutions Request Tracker=1.0.0
Best Practical Solutions Request Tracker=3.0.1
Best Practical Solutions Request Tracker=3.2.1
Best Practical Solutions Request Tracker=3.8.5
Best Practical Solutions Request Tracker=2.0.5.1
Best Practical Solutions Request Tracker=3.4.4
Best Practical Solutions Request Tracker=3.6.8
Best Practical Solutions Request Tracker=1.0.4
Best Practical Solutions Request Tracker=3.0.6
Best Practical Solutions Request Tracker=3.8.6-rc1
Best Practical Solutions Request Tracker=3.0.7
Best Practical Solutions Request Tracker=3.0.7.1
Best Practical Solutions Request Tracker=3.0.12
Best Practical Solutions Request Tracker=3.0.9
Best Practical Solutions Request Tracker=3.8.3
Best Practical Solutions Request Tracker=3.6.1
Best Practical Solutions Request Tracker=3.4.1
Best Practical Solutions Request Tracker=3.8.6
Best Practical Solutions Request Tracker=3.6.4
Best Practical Solutions Request Tracker=2.0.4
Best Practical Solutions Request Tracker=1.0.6
Best Practical Solutions Request Tracker=3.8.1
Best Practical Solutions Request Tracker=3.8.4
Best Practical Solutions Request Tracker=2.0.9
Best Practical Solutions Request Tracker=1.0.3
Best Practical Solutions Request Tracker=2.0.3
Best Practical Solutions Request Tracker=2.0.12
Best Practical Solutions Request Tracker=3.8.7-rc1
Best Practical Solutions Request Tracker=3.4.2

Remedy

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614575

Remedy

http://lists.bestpractical.com/pipermail/rt-announce/2011-February/000186.html

Remedy

http://openwall.com/lists/oss-security/2011/02/22/12

Remedy

http://openwall.com/lists/oss-security/2011/02/22/16

Remedy

http://openwall.com/lists/oss-security/2011/02/22/6

Remedy

https://github.com/bestpractical/rt/commit/057552287159e801535e59b8fbd5bd98d1322069

Remedy

https://github.com/bestpractical/rt/commit/917c211820590950f7eb0521f7f43b31aeed44c4

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2011-1007?

    CVE-2011-1007 is considered a medium severity vulnerability due to its potential to allow credential theft on unattended workstations.

  • How do I fix CVE-2011-1007?

    To fix CVE-2011-1007, upgrade to RT version 3.8.9 or later, which addresses the login form redirection issue.

  • Who is affected by CVE-2011-1007?

    CVE-2011-1007 affects users of Best Practical Solutions RT versions prior to 3.8.9, including specific versions like 3.0.4 and 2.0.7.

  • What type of attack does CVE-2011-1007 facilitate?

    CVE-2011-1007 facilitates a local attack where an attacker can exploit the absence of proper session management to retrieve login credentials.

  • Is a user login safe in RT versions affected by CVE-2011-1007?

    User logins in affected RT versions are not safe due to the vulnerability allowing attackers to use the browser's back button to resubmit the login form.

Company

Resources

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203