View online: https://www.drupal.org/node/2854980
* Advisory ID: DRUPAL-SA-CONTRIB-2017-022 * Project: Views [1] (third-party module) * Version: 7.x * Date: 2017-February-22 * Security risk: 10/25 ( Moderately Critical) AC:Complex/A:None/CI:Some/II:None/E:Theoretical/TD:Uncommon [2] * Vulnerability: Access bypass
-------- DESCRIPTION ---------------------------------------------------------
The Views module allows site builders to create listings of various data in the Drupal database.
The Views module fails to add the required query tags to listings of Taxonomy Terms, which could cause private data stored on Taxonomy Terms to be leaked to users without permision to view it.
This is mitigated by the fact that a View must exist that lists Taxonomy Terms which contain private data. If all the data on Taxonomy Terms is public or there are no applicable Views, then your site is unaffected.
-------- 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.14.
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.15 [5]
Also see the Views [6] project page.
-------- REPORTED BY ---------------------------------------------------------
* Chris Thornett [7]
-------- FIXED BY ------------------------------------------------------------
* Chris Thornett [8] * dawehner [9] * xjm [10] of the Drupal Security Team
-------- COORDINATED BY ------------------------------------------------------
* Michael Hess [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/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/project/views/releases/7.x-3.15 [6] https://www.drupal.org/project/views [7] https://www.drupal.org/user/2352928 [8] https://www.drupal.org/user/2352928 [9] https://www.drupal.org/u/dawehner [10] https://www.drupal.org/u/xjm [11] https://www.drupal.org/u/mlhess [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