medium
4.3
CWE
310
Advisory Published
CVE Published
Updated

CVE-2011-0009

First published: Mon Jan 24 2011(Updated: )

Best Practical Solutions RT 3.x before 3.8.9rc2 and 4.x before 4.0.0rc4 uses the MD5 algorithm for password hashes, which makes it easier for context-dependent attackers to determine cleartext passwords via a brute-force attack on the database.

Credit: secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
Best Practical Solutions Request Tracker=3.5.5
Best Practical Solutions Request Tracker=3.0.4
Best Practical Solutions Request Tracker=3.2.1-rc1
Best Practical Solutions Request Tracker=3.6.0-pre1
Best Practical Solutions Request Tracker=3.4.0-rc2
Best Practical Solutions Request Tracker=3.0.8
Best Practical Solutions Request Tracker=3.4.2-rc2
Best Practical Solutions Request Tracker=3.6.4-rc2
Best Practical Solutions Request Tracker=3.8.8-rc2
Best Practical Solutions Request Tracker=3.2.1-rc3
Best Practical Solutions Request Tracker=3.2.0-rc4
Best Practical Solutions Request Tracker=3.1.2
Best Practical Solutions Request Tracker=3.4.2-rc1
Best Practical Solutions Request Tracker=3.6.6-rc1
Best Practical Solutions Request Tracker=3.4.5
Best Practical Solutions Request Tracker=3.0.2
Best Practical Solutions Request Tracker=3.5.4
Best Practical Solutions Request Tracker=3.6.7
Best Practical Solutions Request Tracker=3.0.10-rc1
Best Practical Solutions Request Tracker=3.6.2
Best Practical Solutions Request Tracker=3.4.5-rc2
Best Practical Solutions Request Tracker=3.2.2
Best Practical Solutions Request Tracker=3.6.3
Best Practical Solutions Request Tracker=3.1.6
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=3.6.2-rc1
Best Practical Solutions Request Tracker=3.1.11
Best Practical Solutions Request Tracker=3.6.0-pre0
Best Practical Solutions Request Tracker=3.1.10
Best Practical Solutions Request Tracker=3.0.10-pre2
Best Practical Solutions Request Tracker=3.6.5-rc1
Best Practical Solutions Request Tracker=3.6.0
Best Practical Solutions Request Tracker=3.6.6-rc2
Best Practical Solutions Request Tracker=3.8.0
Best Practical Solutions Request Tracker=3.4.0-rc5
Best Practical Solutions Request Tracker=3.4.0
Best Practical Solutions Request Tracker=3.6.3-rc4
Best Practical Solutions Request Tracker=3.8.1-rc1
Best Practical Solutions Request Tracker=3.1.7
Best Practical Solutions Request Tracker=3.4.4-pre2
Best Practical Solutions Request Tracker=3.8.3-rc1
Best Practical Solutions Request Tracker=3.1.13
Best Practical Solutions Request Tracker=3.4.7-rc1
Best Practical Solutions Request Tracker=3.4.0-rc3
Best Practical Solutions Request Tracker=3.6.5-rc2
Best Practical Solutions Request Tracker=3.8.2-rc2
Best Practical Solutions Request Tracker=3.8.0-rc1
Best Practical Solutions Request Tracker=3.4.0-rc4
Best Practical Solutions Request Tracker=3.0.10
Best Practical Solutions Request Tracker=3.8.8-rc3
Best Practical Solutions Request Tracker=3.8.2-rc1
Best Practical Solutions Request Tracker=3.0.10-pre1
Best Practical Solutions Request Tracker=3.1.16
Best Practical Solutions Request Tracker=3.2.3
Best Practical Solutions Request Tracker=3.2.2-rc1
Best Practical Solutions Request Tracker=3.6.3-rc2
Best Practical Solutions Request Tracker=3.5.3
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=3.6.9
Best Practical Solutions Request Tracker=3.6.6
Best Practical Solutions Request Tracker=3.6.1-rc2
Best Practical Solutions Request Tracker=3.6.5
Best Practical Solutions Request Tracker=3.8.1-rc3
Best Practical Solutions Request Tracker=3.4.3-rc2
Best Practical Solutions Request Tracker=3.4.0-rc6
Best Practical Solutions Request Tracker=3.6.2-rc3
Best Practical Solutions Request Tracker=3.4.5-pre1
Best Practical Solutions Request Tracker=3.8.4-rc1
Best Practical Solutions Request Tracker=3.0.1
Best Practical Solutions Request Tracker=3.8.1-rc4
Best Practical Solutions Request Tracker=3.4.4-pre3
Best Practical Solutions Request Tracker=3.2.1
Best Practical Solutions Request Tracker=3.8.5
Best Practical Solutions Request Tracker=3.6.6-rc3
Best Practical Solutions Request Tracker=3.2.3-rc2
Best Practical Solutions Request Tracker=3.4.4
Best Practical Solutions Request Tracker=3.0.11-rc4
Best Practical Solutions Request Tracker=3.5.6
Best Practical Solutions Request Tracker=3.6.4-rc1
Best Practical Solutions Request Tracker=3.6.8
Best Practical Solutions Request Tracker=3.0.6
Best Practical Solutions Request Tracker=3.2.1-rc2
Best Practical Solutions Request Tracker=3.8.1-rc5
Best Practical Solutions Request Tracker=3.1.8
Best Practical Solutions Request Tracker=3.4.6-rc2
Best Practical Solutions Request Tracker=3.4.3-rc1
Best Practical Solutions Request Tracker=3.6.3-rc1
Best Practical Solutions Request Tracker=3.6.0-rc1
Best Practical Solutions Request Tracker=3.8.6-rc1
Best Practical Solutions Request Tracker=3.2.0-rc2
Best Practical Solutions Request Tracker=3.1.12
Best Practical Solutions Request Tracker=3.1.5
Best Practical Solutions Request Tracker=3.8.0-rc3
Best Practical Solutions Request Tracker=3.8.0-rc2
Best Practical Solutions Request Tracker=3.2.0-rc1
Best Practical Solutions Request Tracker=3.1.17
Best Practical Solutions Request Tracker=3.0.7
Best Practical Solutions Request Tracker=3.2.0-rc3
Best Practical Solutions Request Tracker=3.7.86
Best Practical Solutions Request Tracker=3.0.7.1
Best Practical Solutions Request Tracker=3.6.3-rc3
Best Practical Solutions Request Tracker=3.7.80
Best Practical Solutions Request Tracker=3.1.15
Best Practical Solutions Request Tracker=3.0.12
Best Practical Solutions Request Tracker=3.6.2-rc4
Best Practical Solutions Request Tracker=3.0.9
Best Practical Solutions Request Tracker=3.4.4-pre1
Best Practical Solutions Request Tracker=3.8.3
Best Practical Solutions Request Tracker<=3.8.9
Best Practical Solutions Request Tracker=3.7.1
Best Practical Solutions Request Tracker=3.1.3
Best Practical Solutions Request Tracker=3.6.1
Best Practical Solutions Request Tracker=3.4.0-rc1
Best Practical Solutions Request Tracker=3.4.1
Best Practical Solutions Request Tracker=3.4.5-rc1
Best Practical Solutions Request Tracker=3.2.3-rc1
Best Practical Solutions Request Tracker=3.8.6
Best Practical Solutions Request Tracker=3.6.4
Best Practical Solutions Request Tracker=3.5.7
Best Practical Solutions Request Tracker=3.6.0-rc3
Best Practical Solutions Request Tracker=3.8.1
Best Practical Solutions Request Tracker=3.8.4
Best Practical Solutions Request Tracker=3.7.5
Best Practical Solutions Request Tracker=3.8.1-rc2
Best Practical Solutions Request Tracker=3.7.85
Best Practical Solutions Request Tracker=3.6.1-rc1
Best Practical Solutions Request Tracker=3.8.3-rc2
Best Practical Solutions Request Tracker=3.6.2-rc5
Best Practical Solutions Request Tracker=3.4.6-rc1
Best Practical Solutions Request Tracker=3.6.1-pre2
Best Practical Solutions Request Tracker=3.0.11-rc2
Best Practical Solutions Request Tracker=3.2.1-rc4
Best Practical Solutions Request Tracker=3.5.2
Best Practical Solutions Request Tracker=3.6.0-rc2
Best Practical Solutions Request Tracker=3.1.4
Best Practical Solutions Request Tracker=3.0.11-rc3
Best Practical Solutions Request Tracker=3.8.7-rc1
Best Practical Solutions Request Tracker=3.1.14
Best Practical Solutions Request Tracker=3.4.2
Best Practical Solutions Request Tracker=3.5.1
Best Practical Solutions Request Tracker=4.0.0-rc3
Best Practical Solutions Request Tracker=4.0.0-rc2
Best Practical Solutions Request Tracker=4.0.0-rc1

Remedy

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

Remedy

http://lists.bestpractical.com/pipermail/rt-announce/2011-January/000185.html

Remedy

https://bugzilla.redhat.com/show_bug.cgi?id=672250

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

    CVE-2011-0009 is considered a high severity vulnerability due to the use of the MD5 algorithm for password hashing, which can be exploited through brute-force attacks.

  • How do I fix CVE-2011-0009?

    To fix CVE-2011-0009, upgrade to Request Tracker versions 3.8.9rc2 or 4.0.0rc4 or later, which use stronger password hashing algorithms.

  • What software versions are affected by CVE-2011-0009?

    CVE-2011-0009 affects Best Practical Solutions RT versions before 3.8.9rc2 and 4.0.0rc4.

  • Who exploits CVE-2011-0009?

    CVE-2011-0009 can be exploited by context-dependent attackers, who may gain access to user passwords via brute-force methods.

  • What impact does CVE-2011-0009 have on users?

    The impact of CVE-2011-0009 may lead to unauthorized access to user accounts if attacker successfully determines cleartext passwords.

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