Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
By Drupal Security Team on
- Advisory ID: DRUPAL-SA-CONTRIB-2013-012
- Project: Google Authenticator login (third-party module)
- Version: 7.x
- Date: 2013-January-30
- Security risk: Highly critical
- 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
- CVE-2013-0258
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 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
Also see the Google Authenticator login project page.
Reported by
Fixed by
- attiks the module maintainer
Coordinated by
- Heine Deelstra of the Drupal Security Team
- Greg Knaddison 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.
Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.
