First published: Mon Jan 24 2011(Updated: )
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] <a href="http://lists.bestpractical.com/pipermail/rt-announce/2011-January/000185.html">http://lists.bestpractical.com/pipermail/rt-announce/2011-January/000185.html</a> [2] <a href="http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610850">http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610850</a> [3] <a href="http://www.debian.org/security/2011/dsa-2150">http://www.debian.org/security/2011/dsa-2150</a> RT Development Snapshots archive URL: [4] <a href="http://download.bestpractical.com/pub/rt/devel/">http://download.bestpractical.com/pub/rt/devel/</a>
Affected Software | Affected Version | How to fix |
---|---|---|
Request Tracker |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-672250 is considered high due to the potential for local attackers to exploit weak password hashing.
To fix REDHAT-BUG-672250, update to the latest version of Request Tracker that implements a more secure password hashing algorithm.
Users and administrators of the Request Tracker system are primarily affected by REDHAT-BUG-672250.
The risks associated with REDHAT-BUG-672250 include unauthorized access to user accounts through brute force password attacks.
Yes, a patch is available for REDHAT-BUG-672250 in the latest release of Request Tracker.