alexmv at bestpractical
Jan 19, 2011, 3:10 PM
Post #1 of 1
All released versions of RT from 3.0.0 through 3.8.9rc1 use an
Security vulnerability in RT 3.0 and up
insecure hashing algorithm to store user passwords. If an attacker is
able to gain read access to RT's database, it would be possible for
the attacker to brute-force the hash and discover users' passwords.
CVE-2011-0009 has been assigned to this vulnerability.
This vulnerability may affect you even if your RT instance
authenticates against an external source. If your RT instance has ever
stored user passwords in the database, their presence is a risk.
For releases prior to RT 3.8.9, we've built an extension called
RT::Extension::SaltedPasswords to mitigate this. This extension
alters RT's functionality to use salted SHA-256 to store passwords
instead of RT's current default. It also includes a tool to detect
and upgrade all existing MD5 passwords to the new SHA-256 storage
format. We've tested this extension with recent releases of RT 3.6
and RT 3.8.
You can download this extension from:
RT 3.8.9rc2 and 4.0.0rc4, to be released today, also close this
vulnerability by moving to a password storage based on salted SHA
hashes. The former uses SHA-256 with a four-byte salt, identical to
what the above extension provides; the latter extends the size of the
password field and uses SHA-512 with a 16-byte salt. We are
additionally considering moving RT 4.0 to the same multiple-round
SHA-512 algorithm that modern Linux crypt() uses.
We wish to thank Chris Ball <cjb [at] laptop> for bringing this to our
attention in a diligent and professional manner.
If you need help resolving this issue locally, please contact us at
sales [at] bestpractical for more information.