View online: https://www.drupal.org/node/2480327
* Advisory ID: DRUPAL-SA-CONTRIB-2015-103 * Project: Views [1] (third-party module) * Version: 7.x * Date: 2015-April-29 * Security risk: 15/25 ( Critical) AC:None/A:None/CI:Some/II:None/E:Theoretical/TD:All [2] * 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.
.... Access bypass due cache inconsistency
Due to an issue in the caching mechanism of Views it's possible that configured filters loose their effect. This can lead to exposure of content that otherwise would be hidden from visitors. This vulnerability is mitigated by the fact that it can't be exploited directly but occurs when certain prerequisites meet. Systems that use in-memory cache backends like redis / memcache are more likely to be affected by this issue. This is due the common strategy used to free cache space if the configured memory limit of the cache is reached.
-------- 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 from 7.x-3.5 to 7.x-3.11.
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.11 [5]
Also see the Views [6] project page.
-------- REPORTED BY ---------------------------------------------------------
* Peter Philipp [7] * Daniel Wehner [8]the module maintainer
-------- FIXED BY ------------------------------------------------------------
* Peter Philipp [9]
-------- COORDINATED BY ------------------------------------------------------
* 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 https://www.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].
Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [15]
[1] https://www.drupal.org/project/views [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/views [5] https://www.drupal.org/node/2480259 [6] https://www.drupal.org/project/views [7] https://www.drupal.org/user/762870 [8] https://www.drupal.org/user/99340 [9] https://www.drupal.org/user/762870 [10] https://www.drupal.org/u/greggles [11] https://www.drupal.org/contact [12] https://www.drupal.org/security-team [13] https://www.drupal.org/writing-secure-code [14] https://www.drupal.org/security/secure-configuration [15] https://twitter.com/drupalsecurity