View online: https://www.drupal.org/SA-CORE-2015-001

* Advisory ID: DRUPAL-SA-CORE-2015-001
* Project: Drupal core [1]
* Version: 6.x, 7.x
* Date: 2015-March-18
* Security risk: 14/25 ( Moderately Critical)
AC:Complex/A:None/CI:Some/II:Some/E:Theoretical/TD:Default [2]
* Vulnerability: Access bypass, Open Redirect, Multiple vulnerabilities

——– DESCRIPTION
———————————————————

…. Access bypass (Password reset URLs – Drupal 6 and 7)

Password reset URLs can be forged under certain circumstances, allowing an
attacker to gain access to another user’s account without knowing the
account’s password.

In Drupal 7, this vulnerability is mitigated by the fact that it can only be
exploited on sites where accounts have been imported or programmatically
edited in a way that results in the password hash in the database being the
same for multiple user accounts. In Drupal 6, it can additionally be
exploited on sites where administrators have created multiple new user
accounts with the same password via the administrative interface, or where
accounts have been imported or programmatically edited in a way that results
in the password hash in the database being empty for at least one user
account.

Drupal 6 sites that have empty password hashes, or a password field with a
guessable string in the database, are especially prone to this vulnerability.
This could apply to sites that use external authentication so that the
password field is set to a fixed, invalid value.

…. Open redirect (Several vectors including the “destination” URL parameter
– Drupal 6 and 7)

Drupal core and contributed modules frequently use a “destination” query
string parameter in URLs to redirect users to a new destination after
completing an action on the current page. Under certain circumstances,
malicious users can use this parameter to construct a URL that will trick
users into being redirected to a 3rd party website, thereby exposing the
users to potential social engineering attacks.

In addition, several URL-related API functions in Drupal 6 and 7 can be
tricked into passing through external URLs when not intending to, potentially
leading to additional open redirect vulnerabilities.

This vulnerability is mitigated by the fact that many common uses of the
“destination” parameter are not susceptible to the attack. However, all
confirmation forms built using Drupal 7’s form API are vulnerable via the
Cancel action that appears at the bottom of the form, and some Drupal 6
confirmation forms are vulnerable too.

——– CVE IDENTIFIER(S) ISSUED
——————————————–

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

——– VERSIONS AFFECTED
—————————————————

* Drupal core 6.x versions prior to 6.35
* Drupal core 7.x versions prior to 7.35

——– SOLUTION
————————————————————

Install the latest version:

* If you use the Drupal 6.x, upgrade to Drupal core 6.35 [4]
* If you use the Drupal 7.x, upgrade to Drupal core 7.35 [5]

Also see the Drupal core [6] project page.

——– REPORTED BY
———————————————————

Access bypass via password reset URLs:

* Daniël Smidt [7]

Open redirect via vectors including the “destination” URL parameter:

* Hunter Fox [8] of the Drupal Security Team
* Vlad Stratulat [9]
* Michael Smith [10]
* Dave Reid [11] of the Drupal Security Team

——– FIXED BY
————————————————————

Access bypass via password reset URLs:

* Klaus Purer [12] of the Drupal Security Team
* David Rothstein [13] of the Drupal Security Team
* Peter Wolanin [14] of the Drupal Security Team
* Ben Dougherty [15], provisional member of the Drupal Security Team

Open redirect via vectors including the “destination” URL parameter:

* Klaus Purer [16] of the Drupal Security Team
* David Rothstein [17] of the Drupal Security Team
* Hunter Fox [18] of the Drupal Security Team
* Tom Phethean [19], provisional member of the Drupal Security Team
* David Stoline [20] of the Drupal Security Team
* Damien McKenna [21], provisional member of the Drupal Security Team
* Pere Orga [22] of the Drupal Security Team
* Ben Dougherty [23], provisional member of the Drupal Security Team

——– COORDINATED BY
——————————————————

* The Drupal Security Team [24]

——– CONTACT AND MORE INFORMATION
—————————————-

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

Learn more about the Drupal Security team and their policies [26], writing
secure code for Drupal [27], and securing your site [28].

Follow the Drupal Security Team on Twitter at
https://twitter.com/drupalsecurity [29]

[1] https://www.drupal.org/project/drupal
[2] https://www.drupal.org/security-team/risk-levels
[3] http://cve.mitre.org/
[4] https://www.drupal.org/drupal-6.35-release-notes
[5] https://www.drupal.org/drupal-7.35-release-notes
[6] https://www.drupal.org/project/drupal
[7] https://www.drupal.org/user/198330
[8] https://www.drupal.org/u/hefox
[9] https://www.drupal.org/user/1006458
[10] https://www.drupal.org/user/1291584
[11] https://www.drupal.org/u/dave-reid
[12] https://www.drupal.org/u/klausi
[13] https://www.drupal.org/u/David_Rothstein
[14] https://www.drupal.org/u/pwolanin
[15] http://drupal.org/u/benjy
[16] https://www.drupal.org/u/klausi
[17] https://www.drupal.org/u/David_Rothstein
[18] https://www.drupal.org/u/hefox
[19] http://drupal.org/user/881620
[20] http://drupal.org/user/329570
[21] https://www.drupal.org/user/108450
[22] https://www.drupal.org/u/pere-orga
[23] http://drupal.org/u/benjy
[24] https://www.drupal.org/security-team
[25] https://www.drupal.org/contact
[26] https://www.drupal.org/security-team
[27] https://www.drupal.org/writing-secure-code
[28] https://www.drupal.org/security/secure-configuration
[29] https://twitter.com/drupalsecurity

_______________________________________________
Security-news mailing list
Security-news@drupal.org
Unsubscribe at https://lists.drupal.org/mailman/listinfo/security-news
7e