- Advisory ID: DRUPAL-SA-CONTRIB-2015-039
- Project: Views (third-party module)
- Version: 6.x, 7.x
- Date: 2015-February-11
- Security risk: 8/25 ( Less Critical) AC:Basic/A:Admin/CI:Some/II:None/E:Theoretical/TD:Uncommon
- Vulnerability: Multiple vulnerabilities
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.
Open redirect vulnerability
The module does not sanitize user provided URLs when processing the page to break the lock on Views being edited, thereby exposing an open redirect attack vector.
This vulnerability is mitigated by the fact that the Views UI submodule must be enabled.
Access bypass vulnerability
The module does not protect the default Views configurations that ship with the module sufficiently, thereby exposing possibly protected information to unprivileged users.
This vulnerability is mitigated by the fact that it only affects sites that have not granted the common "access content" or "access comments" permission to untrusted users. Furthermore, these default views configurations are disabled by default and must be enabled by an administrator.
CVE identifier(s) issued
- Open redirect: CVE-2015-3378
- Access bypass: CVE-2015-3379
- Views 6.x-2.x versions prior to 6.x-2.18.
- Views 6.x-3.x versions prior to 6.x-3.2.
- Views 7.x-3.x versions prior to 7.x-3.10.
Drupal core is not affected. If you do not use the contributed Views module,
there is nothing you need to do.
Install the latest version:
- If you use the Views module for Drupal 6.x, upgrade to Views 6.x-2.18 or Views 6.x-3.2
- If you use the Views module for Drupal 7.x, upgrade to Views 7.x-3.10
Also see the Views project page.
- Open Redirect: Klaus Purer of the Drupal Security Team
- Access bypass: Daniel Wehner the module maintainer
- Daniel Wehner the module maintainer
- Klaus Purer 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.
Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity