View online: https://www.drupal.org/node/2902604
* Advisory ID: DRUPAL-SA-CONTRIB-2014-0XX * Project: Views [1] (third-party module) * Version: 7.x, 8.x * Date: 2017-August-16 * Security risk: 14/25 ( Moderately Critical) AC:None/A:None/CI:Some/II:None/E:Theoretical/TD:Default [2] * Vulnerability: Access bypass
-------- DESCRIPTION ---------------------------------------------------------
When creating a view, you can optionally use Ajax to update the displayed data via filter parameters. The views subsystem/module did not restrict access to the Ajax endpoint to only views configured to use Ajax. This is mitigated if you have access restrictions on the view.
It is best practice to always include some form of access restrictions on all views, even if you are using another module to display them.
-------- 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 versions prior to 7.x-3.17.
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.17 [5]
Also see the Views [6] project page.
-------- REPORTED BY ---------------------------------------------------------
* Maxim Podorov [7]
-------- FIXED BY ------------------------------------------------------------
* Klaus Purer [8] * Daniel Wehner [9] * Michael Hess [10] of the Drupal Security Team * Len Swaneveld [11] * Wim Leers [12] * Peter Wolanin [13] of the Drupal Security Team
-------- COORDINATED BY ------------------------------------------------------
* Michael Hess [14] 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 [15].
Learn more about the Drupal Security team and their policies [16], writing secure code for Drupal [17], and securing your site [18].
Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [19]
[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.17 [6] https://www.drupal.org/project/views [7] https://www.drupal.org/u/maximpodorov [8] https://www.drupal.org/u/klausi [9] https://www.drupal.org/u/dawehner [10] https://www.drupal.org/u/mlhess [11] https://www.drupal.org/user/690914 [12] https://www.drupal.org/user/99777 [13] https://www.drupal.org/u/pwolanin [14] https://www.drupal.org/u/mlhess [15] https://www.drupal.org/contact [16] https://www.drupal.org/security-team [17] https://www.drupal.org/writing-secure-code [18] https://www.drupal.org/security/secure-configuration [19] https://twitter.com/drupalsecurity