View online: https://drupal.org/node/2271809
* Advisory ID: DRUPAL-SA-CONTRIB-2014-054 * Project: Views [1] (third-party module) * Version: 7.x * Date: 2014-May-21 * Security risk: Moderately critical [2] * Exploitable from: Remote * Vulnerability: Access bypass
-------- DESCRIPTION ---------------------------------------------------------
The Views module provides a flexible method for Drupal site designers to control how lists and tables of content, users, taxonomy terms and other data are presented.
The module doesn't sufficiently check handler access when returning the list of handlers from view_plugin_display::get_handlers(). The most critical code (access plugins and field output) is unaffected - only area handlers, the get_field_labels() method, token replacement, and some relationship handling are susceptible.
-------- CVE IDENTIFIER(S) ISSUED --------------------------------------------
* /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./
-------- VERSIONS AFFECTED ---------------------------------------------------
* Views 7.x-3.x versions prior to 7.x-3.8.
Drupal core is not affected. If you do not use the contributed Views [4] module, there is nothing you need to do.
-------- SOLUTION ------------------------------------------------------------
Install the latest version:
* If you use the Views module for Drupal 7.x, upgrade to Views 7.x-3.8 [5]
Also see the Views [6] project page.
-------- REPORTED BY ---------------------------------------------------------
* Tim Plunkett [7]
-------- FIXED BY ------------------------------------------------------------
* Tim Plunkett [8] and Daniel Wehner [9], the module maintainers * David Snopek [10] of the Drupal Security Team
-------- COORDINATED BY ------------------------------------------------------
* David Snopek [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].
Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [16]
[1] http://drupal.org/project/views [2] http://drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] http://drupal.org/project/views [5] https://drupal.org/node/2271305 [6] http://drupal.org/project/views [7] https://drupal.org/user/241634 [8] https://drupal.org/user/241634 [9] https://drupal.org/user/99340 [10] https://drupal.org/user/266527 [11] https://drupal.org/user/266527 [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 [16] https://twitter.com/drupalsecurity