medium
4
CWE
264
Advisory Published
Updated

CVE-2011-1008

First published: Mon Feb 28 2011(Updated: )

Scrips_Overlay.pm in Best Practical Solutions RT before 3.8.9 does not properly restrict access to a TicketObj in a Scrip after a CurrentUser change, which allows remote authenticated users to obtain sensitive information via unspecified vectors, as demonstrated by custom-field value information, related to SQL logging.

Credit: secalert@redhat.com

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

Remedy

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

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/2338cd19ed7a7f4c1e94f639ab2789d6586d01f3

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-1008?

    CVE-2011-1008 is classified as a moderate severity vulnerability.

  • How do I fix CVE-2011-1008?

    To fix CVE-2011-1008, upgrade to RT version 3.8.9 or later.

  • What software is affected by CVE-2011-1008?

    CVE-2011-1008 affects several versions of Best Practical's RT, specifically versions prior to 3.8.9.

  • What type of vulnerability is CVE-2011-1008?

    CVE-2011-1008 is an access control vulnerability that can allow unauthorized information access.

  • What are the symptoms of CVE-2011-1008 exploitation?

    Exploitation of CVE-2011-1008 may lead to unauthorized access to sensitive ticket information for authenticated users.

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