View online: https://www.drupal.org/node/2403351
* Advisory ID: DRUPAL-SA-CONTRIB-2015-004 * Project: Context [1] (third-party module) * Version: 7.x * Date: 2015-January-07 * Security risk: 9/25 ( Less Critical) AC:Basic/A:None/CI:None/II:None/E:Theoretical/TD:Default [2] * Vulnerability: Open Redirect
-------- DESCRIPTION ---------------------------------------------------------
Context allows you to manage contextual conditions and reactions for different portions of your site.
Context UI module wasn't checking for external URLs in the HTTP GET destination parameter when redirecting users that are activating/deactivating the Context UI inline editor dialog, thereby leading to an Open Redirect vulnerability.
This vulnerability is mitigated by the fact that the victim must have the permission "administer contexts" and that Context UI module must be enabled.
-------- CVE IDENTIFIER(S) ISSUED --------------------------------------------
* /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./
-------- VERSIONS AFFECTED ---------------------------------------------------
* Context 7.x-3.x versions prior to 7.x-3.6
Drupal core is not affected. If you do not use the contributed Context [4] module, there is nothing you need to do.
-------- SOLUTION ------------------------------------------------------------
Install the latest version: * If you use the Context module for Drupal 7, upgrade to Context 7.x-3.6 [5]
Also see the Context [6] project page.
-------- REPORTED BY ---------------------------------------------------------
* Pere Orga [7] provisional member of the Drupal Security Team
-------- FIXED BY ------------------------------------------------------------
* Pere Orga [8] provisional member of the Drupal Security Team * Chris Johnson [9], module maintainer * Yonas Yanfa [10], module maintainer
-------- COORDINATED BY ------------------------------------------------------
* Owen Barton [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 https://www.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].
Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [16]
[1] https://www.drupal.org/project/context [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/context [5] https://www.drupal.org/node/2402779 [6] https://www.drupal.org/project/context [7] https://www.drupal.org/user/2301194 [8] https://www.drupal.org/user/2301194 [9] https://www.drupal.org/user/8134 [10] https://www.drupal.org/user/7089 [11] https://www.drupal.org/user/19668 [12] https://www.drupal.org/contact [13] https://www.drupal.org/security-team [14] https://www.drupal.org/writing-secure-code [15] https://www.drupal.org/security/secure-configuration [16] https://twitter.com/drupalsecurity