[Security-news] SA-CONTRIB-2012-159 - Password policy - Information leakage of hashed passwords

[security-news at drupal.org]

View online: https://drupal.org/node/1828340

  * Advisory ID: DRUPAL-SA-CONTRIB-2012-159
  * Project: Password policy [1] (third-party module)
  * Version: 6.x, 7.x
  * Date: 2012-October-31
  * Security risk: Moderately critical [2]
  * Exploitable from: Remote
  * Vulnerability: Information Disclosure

-------- DESCRIPTION  
---------------------------------------------------------

This module provides a way to specify a certain level of password complexity
(aka. "password hardening") for user passwords on a system by defining a
password policy.

The Password policy module allows administrators to request users to enter a
new password that does not match any of the previous X passwords they have
used (X is determined by the site configuration). If this feature is enabled,
a malicious user with the capability to view another user's HTTP traffic can
discover the hashed version of their password. This issue is more of a risk
for Drupal 6 sites that use the default md5 password encryption.

This issue only affects sites that use the module's "previous passwords"
feature, and fail to encrypt their users' HTTP transactions with SSL/TLS.

CVE: Requested

-------- VERSIONS AFFECTED  
---------------------------------------------------

  * Password policy 6.x-1.x versions prior to 6.x-1.5.
  * Password policy 7.x-1.x versions prior to 7.x-1.3.

Drupal core is not affected. If you do not use the contributed Password
policy [3] module, there is nothing you need to do.

-------- SOLUTION  
------------------------------------------------------------

Install the latest version:

  * If you use the Password policy module for Drupal 6.x, upgrade to Password
    policy 6.x-1.5 [4]
  * If you use the Password policy module for Drupal 7.x, upgrade to Password
    policy 7.x-1.3 [5]

Also see the Password policy [6] project page.

-------- REPORTED BY  
---------------------------------------------------------

  * Alexis Wilke [7]

-------- FIXED BY  
------------------------------------------------------------

  * Mark Shropshire [8]

-------- COORDINATED BY  
------------------------------------------------------

  * Greg Knaddison [9] of the Drupal Security Team
  * Michael Hess [10] of the Drupal Security Team
  * Damien Tournoud [11] of the Drupal Security Team

-------- CONTACT AND MORE INFORMATION  
----------------------------------------

The Drupal security team can be reached at security at drupal.org or via the
contact form at http://drupal.org/contact [12].

Learn more about the Drupal Security team and their policies [13], writing
secure code for Drupal [14], and securing your site [15].


[1] http://drupal.org/project/password_policy
[2] http://drupal.org/security-team/risk-levels
[3] http://drupal.org/project/password_policy
[4] https://drupal.org/node/1828130
[5] https://drupal.org/node/1828142
[6] http://drupal.org/project/password_policy
[7] http://drupal.org/user/356197
[8] http://drupal.org/user/14767
[9] http://drupal.org/user/36762
[10] http://drupal.org/user/102818
[11] http://drupal.org/user/22211
[12] http://drupal.org/contact
[13] http://drupal.org/security-team
[14] http://drupal.org/writing-secure-code
[15] http://drupal.org/security/secure-configuration