CVE-2011-0009: Medium severity best practical solutions request tracker vulnerability
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.
Other sources
It was found that Request Tracker, a ticket tracking and management system, stored user passwords in its database by using insufficiently secure hashing algorithm. A local attacker, able to gain read access to the RT's database could use this flaw to conduct brute force password guessing attacks, potentially leading to disclosure of users' passwords.
References: [1] http://lists.bestpractical.com/pipermail/rt-announce/2011-January/000185.html [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610850 [3] http://www.debian.org/security/2011/dsa-2150
RT Development Snapshots archive URL: [4] http://download.bestpractical.com/pub/rt/devel/
— Red Hat
Affected Software
Remediation
Patch Available
Patch Available
Event History
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.