Date: Wed, 30 Jan 2013 18:30:27 +0000 (UTC)
From: security-news@...pal.org
To: security-news@...pal.org
Subject: [Security-news] SA-CONTRIB-2013-012 - Google
	Authenticator login -	Access Bypass

View online: http://drupal.org/node/1903282

  * Advisory ID: DRUPAL-SA-CONTRIB-2013-012
  * Project: Google Authenticator login [1] (third-party module)
  * Version: 7.x
  * Date: 2013-January-30
  * Security risk: Highly critical [2]
  * Exploitable from: Remote
  * Vulnerability: Access bypass

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

This module will allow you to add Time-based One-time Password Algorithm
(also called "Two Step Authentication" or "Multi-Factor Authentication")
support to user logins.

Users with the permission to use multi-factor authentication need to
associate a Google Authenticator token with their acount before they can use
the multi-factor authentication for login. If this step is not done or not
completed, their accounts can be logged-in to by supplying the username only
due to a logic bug in the module's validation. This means that when an
administrator enables the module and grants the permission to use
multi-factor authentication all user accounts with that permission can be
logged-in to via the username.


-------- CVE IDENTIFIER(S) ISSUED  
--------------------------------------------

  * /A CVE identifier [3] will be requested, and added upon issuance, in
    accordance with Drupal Security Team processes./

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

  * All 7.x versions prior to 7.x-1.3.

Drupal core is not affected. If you do not use the contributed Google
Authenticator login [4] module, there is nothing you need to do.

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

Install the latest version:

  * If you use the Google Authenticator login module for Drupal 7.x, upgrade
    to Google Authenticator login 7.x-1.3 [5]

Also see the Google Authenticator login [6] project page.

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

  * Patrick C. [7]

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

  * attiks [8] the module maintainer

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

  * Heine Deelstra [9] of the Drupal Security Team
  * Greg Knaddison [10] 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 [11].

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


[1] http://drupal.org/project/ga_login
[2] http://drupal.org/security-team/risk-levels
[3] http://cve.mitre.org/
[4] http://drupal.org/project/ga_login
[5] http://drupal.org/node/1902102
[6] http://drupal.org/project/ga_login
[7] https://drupal.org/user/127758
[8] http://drupal.org/user/105002
[9] http://drupal.org/user/17943
[10] http://drupal.org/user/36762
[11] http://drupal.org/contact
[12] http://drupal.org/security-team
[13] http://drupal.org/writing-secure-code
[14] http://drupal.org/security/secure-configuration

_______________________________________________
Security-news mailing list
Security-news@...pal.org
Unsubscribe at http://lists.drupal.org/mailman/listinfo/security-news

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/

Powered by blists - more mailing lists